From: Joanne Koong <joannelkoong@gmail.com>
To: brauner@kernel.org
Cc: willy@infradead.org, djwong@kernel.org, hch@infradead.org,
bfoster@redhat.com, linux-fsdevel@vger.kernel.org
Subject: [PATCH v4 0/1] iomap: fix invalid folio access after folio_end_read()
Date: Fri, 23 Jan 2026 15:56:16 -0800 [thread overview]
Message-ID: <20260123235617.1026939-1-joannelkoong@gmail.com> (raw)
This patch is on top of Christian's vfs.fixes tree.
Changelog
---------
v3:
https://lore.kernel.org/linux-fsdevel/20260116200427.1016177-1-joannelkoong@gmail.com/
* Make commit message more descriptive (Christoph)
* Also remove "+1" bias (Matthew)
* Account for non-readahead reads as well (me)
v2:
https://lore.kernel.org/linux-fsdevel/20260116015452.757719-1-joannelkoong@gmail.com/
* Fix incorrect spacing (Matthew)
* Reword commit title and message (Matthew)
v1:
https://lore.kernel.org/linux-fsdevel/20260114180255.3043081-1-joannelkoong@gmail.com/
* Invalidate ctx->cur_folio instead of retaining readahead caller refcount (Matthew)
Joanne Koong (1):
iomap: fix invalid folio access after folio_end_read()
fs/iomap/buffered-io.c | 69 ++++++++++++++++++++++--------------------
1 file changed, 37 insertions(+), 32 deletions(-)
--
2.47.3
next reply other threads:[~2026-01-23 23:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 23:56 Joanne Koong [this message]
2026-01-23 23:56 ` [PATCH v4 1/1] iomap: fix invalid folio access after folio_end_read() Joanne Koong
2026-01-26 5:46 ` Christoph Hellwig
2026-01-26 14:55 ` Matthew Wilcox
2026-01-26 14:59 ` Christoph Hellwig
2026-01-26 21:36 ` Joanne Koong
2026-01-26 21:42 ` Matthew Wilcox
2026-01-26 22:10 ` Joanne Koong
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=20260123235617.1026939-1-joannelkoong@gmail.com \
--to=joannelkoong@gmail.com \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.org \
/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