From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: fbdev: defio: Move variable state into struct fb_deferred_io_state
Date: Fri, 27 Feb 2026 15:29:26 +1000 [thread overview]
Message-ID: <review-patch3-20260224082657.207284-4-tzimmermann@suse.de> (raw)
In-Reply-To: <20260224082657.207284-4-tzimmermann@suse.de>
Patch Review
Clean refactoring moving `open_count`, `mapping`, and `pagereflist` from the driver-visible `struct fb_deferred_io` to the internal `struct fb_deferred_io_state`.
**Good improvements:**
- `BUG_ON(!info->fbdefio->mapping)` replaced with `fb_WARN_ON_ONCE(info, !fbdefio_state->mapping)` — converting BUG_ON to WARN is the right call here.
- `WARN_ON(!list_empty(&fbdefio_state->pagereflist))` added in `fb_deferred_io_state_release` — good sanity check.
- `INIT_LIST_HEAD(&fbdefio_state->pagereflist)` properly moved to `fb_deferred_io_state_alloc`.
**Minor nit:** The added forward declaration:
```c
struct address_space;
```
is technically redundant since `<linux/pagemap.h>` is already included (which pulls in `<linux/fs.h>` where `struct address_space` is defined). It's harmless and documents the dependency, but could be dropped.
The removal of `fbdefio->mapping = NULL` from `fb_deferred_io_cleanup` is correct since `mapping` is now in the state struct, and the state's `info` pointer is set to NULL under the lock, which prevents any access to `mapping` after cleanup.
No issues with this patch.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-27 5:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 8:25 [PATCH v2 0/4] fbdev: defio: Protect against device/module removal Thomas Zimmermann
2026-02-24 8:25 ` [PATCH v2 1/4] fbdev: defio: Disconnect deferred I/O from the lifetime of struct fb_info Thomas Zimmermann
2026-02-27 5:29 ` Claude review: " Claude Code Review Bot
2026-02-24 8:25 ` [PATCH v2 2/4] fbdev: defio: Keep module reference from VMAs Thomas Zimmermann
2026-02-27 5:29 ` Claude review: " Claude Code Review Bot
2026-02-24 8:25 ` [PATCH v2 3/4] fbdev: defio: Move variable state into struct fb_deferred_io_state Thomas Zimmermann
2026-02-27 5:29 ` Claude Code Review Bot [this message]
2026-02-24 8:25 ` [PATCH v2 4/4] fbdev: defio: Move pageref array to " Thomas Zimmermann
2026-02-27 5:29 ` Claude review: " Claude Code Review Bot
2026-02-24 22:02 ` [PATCH v2 0/4] fbdev: defio: Protect against device/module removal Helge Deller
2026-02-27 5:29 ` Claude review: " Claude Code Review Bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=review-patch3-20260224082657.207284-4-tzimmermann@suse.de \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox