public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
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 v2 0/1] iomap: fix readahead folio refcounting race
Date: Thu, 15 Jan 2026 17:54:51 -0800	[thread overview]
Message-ID: <20260116015452.757719-1-joannelkoong@gmail.com> (raw)

This patch is on top of Christian's vfs.fixes tree.

This fixes a race for readahead folios that was introduced by commit
b2f35ac4146d ("iomap: add caller-provided callbacks for read and readahead").

The change in the patch was sanity-tested on fuse and xfs (with large folios
disabled) by running generic/112 for both readahead and read_folio (simulated
by commenting out the ->readahead() callback).

Changelog
---------
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 readahead folio refcounting race

 fs/iomap/buffered-io.c | 23 +++++++++++++++++++++--
 1 file changed, 21 insertions(+), 2 deletions(-)

-- 
2.47.3


             reply	other threads:[~2026-01-16  1:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16  1:54 Joanne Koong [this message]
2026-01-16  1:54 ` [PATCH v2 1/1] iomap: fix readahead folio refcounting race Joanne Koong
2026-01-16  2:52   ` Matthew Wilcox
2026-01-16 18:36     ` Joanne Koong
2026-01-16 21:45       ` Matthew Wilcox
2026-01-16 22:02         ` Joanne Koong
2026-01-17  2:30           ` Darrick J. Wong
2026-01-21  0:34             ` Joanne Koong
2026-01-21  1:07               ` Matthew Wilcox
2026-01-21  4:12                 ` Joanne Koong
2026-01-21  4:42                   ` Matthew Wilcox
2026-01-21  5:51                     ` 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=20260116015452.757719-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