From: Joanne Koong <joannelkoong@gmail.com>
To: brauner@kernel.org
Cc: bfoster@redhat.com, hch@infradead.org, djwong@kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v3 0/2] vfs-6.19.iomap commit 51311f045375 fixups
Date: Tue, 28 Oct 2025 11:11:31 -0700 [thread overview]
Message-ID: <20251028181133.1285219-1-joannelkoong@gmail.com> (raw)
These are two fixups for commit 51311f045375 ("iomap: track pending read
bytes more optimally") in the vfs-6.19.iomap branch. It would be great
if these could get folded into that original commit, if possible.
The fix for the race was locally tested by running generic/051 in a loop on an
xfs filesystem with 1k block size, as reported by Brian in [1].
Thanks,
Joanne
[1] https://lore.kernel.org/linux-fsdevel/20250926002609.1302233-1-joannelkoong@gmail.com/T/#t
Changelog:
v2 -> v3:
Fix the race by adding a bias instead of returning from iomap_read_end() early.
v2: https://lore.kernel.org/linux-fsdevel/20251027181245.2657535-1-joannelkoong@gmail.com/
v1: https://lore.kernel.org/linux-fsdevel/20251024215008.3844068-1-joannelkoong@gmail.com/#t
Joanne Koong (2):
iomap: rename bytes_pending/bytes_accounted to
bytes_submitted/bytes_not_submitted
iomap: fix race when reading in all bytes of a folio
fs/iomap/buffered-io.c | 75 +++++++++++++++++++++++++++++++-----------
1 file changed, 56 insertions(+), 19 deletions(-)
--
2.47.3
next reply other threads:[~2025-10-28 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 18:11 Joanne Koong [this message]
2025-10-28 18:11 ` [PATCH v3 1/2] iomap: rename bytes_pending/bytes_accounted to bytes_submitted/bytes_not_submitted Joanne Koong
2025-10-29 5:56 ` Darrick J. Wong
2025-10-29 8:36 ` Christoph Hellwig
2025-10-29 8:37 ` Christoph Hellwig
2025-10-28 18:11 ` [PATCH v3 2/2] iomap: fix race when reading in all bytes of a folio Joanne Koong
2025-10-29 8:38 ` Christoph Hellwig
2025-10-31 20:34 ` Joanne Koong
2025-10-31 12:39 ` [PATCH v3 0/2] vfs-6.19.iomap commit 51311f045375 fixups Christian Brauner
2025-10-31 20:38 ` 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=20251028181133.1285219-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 \
/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;
as well as URLs for NNTP newsgroup(s).