From: Christoph Hellwig <hch@lst.de>
To: Christian Brauner <brauner@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>
Cc: Kelu Ye <yekelu1@huawei.com>, Yifan Zhao <zhaoyifan28@huawei.com>,
Ritesh Harjani <ritesh.list@gmail.com>,
Joanne Koong <joannelkoong@gmail.com>,
Namjae Jeon <linkinjeon@kernel.org>,
Sungjong Seo <sj1557.seo@samsung.com>,
Hyunchul Lee <hyc.lee@gmail.com>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
Miklos Szeredi <miklos@szeredi.hu>,
fuse-devel@lists.linux.dev, ntfs3@lists.linux.dev,
linux-erofs@lists.ozlabs.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: don't build bios/contexts over multiple iomaps v3
Date: Mon, 29 Jun 2026 14:17:37 +0200 [thread overview]
Message-ID: <20260629121750.3392300-1-hch@lst.de> (raw)
Hi all,
this patch changes how iomap submits bios for reads. The old behavior
to build up bios across iomap was already considered problematic for
a while, but we now ran into a erofs bug because of it, so it's time
to finally fix it.
It would be great to get the fix into 7.2 as the fixed bug can be
triggered by users.
Changes since v2:
- drop an unused argument
- make sure we submit for the same iteration to not leave a landmine
for future changes
Changes since v1:
- don't submit fuse context after each iteration
- consolidate some code to support the above
- fix a bug in the fs PI support found while doing the above
next reply other threads:[~2026-06-29 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:17 Christoph Hellwig [this message]
2026-06-29 12:17 ` [PATCH 1/3] iomap: consolidate bio submission Christoph Hellwig
2026-07-01 13:27 ` Christian Brauner
2026-07-02 10:27 ` Christoph Hellwig
2026-07-07 11:06 ` Christian Brauner
2026-06-29 12:17 ` [PATCH 2/3] fuse: call fuse_send_readpages explicitly from fuse_readahead Christoph Hellwig
2026-06-29 12:17 ` [PATCH 3/3] iomap: submit read bio after each extent Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2026-06-25 12:07 don't build bios/contexts over multiple iomaps v3 Christoph Hellwig
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=20260629121750.3392300-1-hch@lst.de \
--to=hch@lst.de \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=fuse-devel@lists.linux.dev \
--cc=hyc.lee@gmail.com \
--cc=joannelkoong@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=ntfs3@lists.linux.dev \
--cc=ritesh.list@gmail.com \
--cc=sj1557.seo@samsung.com \
--cc=yekelu1@huawei.com \
--cc=zhaoyifan28@huawei.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