From: Andrea Parri <parri.andrea@gmail.com>
To: Christian Brauner <brauner@kernel.org>,
Carlos Maiolino <cem@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Joanne Koong <joannelkoong@gmail.com>,
Brian Foster <bfoster@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Damien Le Moal <dlemoal@kernel.org>,
Hannes Reinecke <hare@suse.de>,
Daniel Gomez <da.gomez@samsung.com>,
Pankaj Raghav <p.raghav@samsung.com>,
Dave Chinner <dchinner@redhat.com>
Cc: Andrea Parri <parri.andrea@gmail.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH v2 0/4] iomap: fix error handling regressions
Date: Thu, 24 Sep 2026 11:11:50 +0200 [thread overview]
Message-ID: <20260924091203.198225-1-parri.andrea@gmail.com> (raw)
Adding Carlos Maiolino to the To: list since patch 2 (new in v2) touches
fs/xfs/ outside the iomap directory.
Fix three independent error handling regressions in iomap:
- clear the writeback context after a failed ->writeback_submit() call,
preventing an already completed ioend from being submitted again;
- preserve an iomap iteration error when iomap_fiemap() has a pending
extent to emit; and
- preserve a direct I/O data path error when sub-block tail zeroing
succeeds.
The three fixes have no ordering dependencies and can be applied or
backported independently. Each issue was reproduced before and after
its respective fix.
Patch 2 is not a fix and carries no stable tag: it adds an XFS error
tag (requested by Christoph) that lets patch 1's ->writeback_submit()
failure be injected without the boot-param hack used for the original
reproduction. I used it to write an xfstest reproducing the bug (list
corruption caught via CONFIG_DEBUG_LIST on an unfixed kernel, clean
writeback failure on a fixed one); I'll send that separately to
fstests@vger.kernel.org once this series is out for review.
Changes since v1:
- Patch 1: reworded the added comment to fit 80 columns (Christoph);
answered Christoph's request for a reproducer in the commit message
(fault-injected ->writeback_submit() failure on a reflinked XFS file,
reliably hits list_add double add on the unfixed kernel); confirmed
with Christoph that the final ->writeback_submit() call in
iomap_writepages() needs no equivalent fix, since wpc is never reused
after it; picked up the version-scoped stable tag Darrick suggested;
picked up Brian's Reviewed-by.
- Patch 2: new, added per Christoph's request.
- Patch 3 (was 2/3): no code change; picked up the version-scoped
stable tag Darrick suggested; picked up Reviewed-by tags from Brian,
Darrick, and Christoph.
- Patch 4 (was 3/3): reworked per Christoph's suggestion to drop the
zerror/ret handling entirely instead of just fixing its type, since
iomap_dio_zero() can only fail via a can't-happen WARN_ON_ONCE()
assert; this also resolves Darrick's question about the local
variable's type, since there's no longer a local variable to type.
Andrea Parri (4):
iomap: don't resubmit an ioend after ->writeback_submit() failed
xfs: add an error tag to inject a ->writeback_submit() failure
iomap: don't lose a fiemap iteration error when emitting the last
extent
iomap: don't lose a failed direct I/O bio's error when zeroing the
tail
fs/iomap/direct-io.c | 19 +++++++------------
fs/iomap/fiemap.c | 8 ++++----
fs/iomap/ioend.c | 10 +++++++++-
fs/xfs/libxfs/xfs_errortag.h | 6 ++++--
fs/xfs/xfs_reflink.c | 5 +++++
5 files changed, 29 insertions(+), 19 deletions(-)
base-commit: 93f51579e7df248780214094418f205253383cc5
--
2.53.0
next reply other threads:[~2026-09-24 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 9:11 Andrea Parri [this message]
2026-09-24 9:11 ` [PATCH v2 1/4] iomap: don't resubmit an ioend after ->writeback_submit() failed Andrea Parri
2026-09-24 9:11 ` [PATCH v2 2/4] xfs: add an error tag to inject a ->writeback_submit() failure Andrea Parri
2026-09-24 9:11 ` [PATCH v2 3/4] iomap: don't lose a fiemap iteration error when emitting the last extent Andrea Parri
2026-09-24 9:11 ` [PATCH v2 4/4] iomap: don't lose a failed direct I/O bio's error when zeroing the tail Andrea Parri
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=20260924091203.198225-1-parri.andrea@gmail.com \
--to=parri.andrea@gmail.com \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=da.gomez@samsung.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=p.raghav@samsung.com \
--cc=stable@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
all inboxes | Powered by JetHome®