From: Thomas Zimmermann <tzimmermann@suse.de>
To: deller@gmx.de, simona@ffwll.ch, jayalk@intworks.biz
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH v2 0/4] fbdev: defio: Protect against device/module removal
Date: Tue, 24 Feb 2026 09:25:53 +0100 [thread overview]
Message-ID: <20260224082657.207284-1-tzimmermann@suse.de> (raw)
There's a long-standing bug in defio where the framebuffer device or
module gets removed while mmap'ed areas of the framebuffer memory
persists in userspace. Page faults in the area then operate on defined
state.
Patches 1 and 2 fix these problems. Patches 3 and 4 build upon the fix
and put defio state into the correct places.
v2:
- use alloc_obj() functions
Thomas Zimmermann (4):
fbdev: defio: Disconnect deferred I/O from the lifetime of struct
fb_info
fbdev: defio: Keep module reference from VMAs
fbdev: defio: Move variable state into struct fb_deferred_io_state
fbdev: defio: Move pageref array to struct fb_deferred_io_state
drivers/video/fbdev/core/fb_defio.c | 266 ++++++++++++++++++++--------
include/linux/fb.h | 9 +-
2 files changed, 195 insertions(+), 80 deletions(-)
base-commit: 1c44015babd759b8e5234084dffcc08a0b784333
--
2.52.0
next reply other threads:[~2026-02-24 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 8:25 Thomas Zimmermann [this message]
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-24 8:25 ` [PATCH v2 2/4] fbdev: defio: Keep module reference from VMAs Thomas Zimmermann
2026-02-24 8:25 ` [PATCH v2 3/4] fbdev: defio: Move variable state into struct fb_deferred_io_state Thomas Zimmermann
2026-02-24 8:25 ` [PATCH v2 4/4] fbdev: defio: Move pageref array to " Thomas Zimmermann
2026-02-24 22:02 ` [PATCH v2 0/4] fbdev: defio: Protect against device/module removal Helge Deller
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=20260224082657.207284-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jayalk@intworks.biz \
--cc=linux-fbdev@vger.kernel.org \
--cc=simona@ffwll.ch \
/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