From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, "Darrick J. Wong" <djwong@kernel.org>,
John Garry <john.g.garry@oracle.com>,
Carlos Maiolino <cem@kernel.org>
Subject: Re: [PATCH 6.17.y 1/2] xfs: fix delalloc write failures in software-provided atomic writes
Date: Fri, 21 Nov 2025 10:47:41 +0100 [thread overview]
Message-ID: <2025112133-bleak-stamina-42ba@gregkh> (raw)
In-Reply-To: <20251109232057.531285-1-sashal@kernel.org>
On Sun, Nov 09, 2025 at 06:20:56PM -0500, Sasha Levin wrote:
> From: "Darrick J. Wong" <djwong@kernel.org>
>
> [ Upstream commit 8d54eacd82a0623a963e0c150ad3b02970638b0d ]
>
> With the 20 Oct 2025 release of fstests, generic/521 fails for me on
> regular (aka non-block-atomic-writes) storage:
>
> QA output created by 521
> dowrite: write: Input/output error
> LOG DUMP (8553 total operations):
> 1( 1 mod 256): SKIPPED (no operation)
> 2( 2 mod 256): WRITE 0x7e000 thru 0x8dfff (0x10000 bytes) HOLE
> 3( 3 mod 256): READ 0x69000 thru 0x79fff (0x11000 bytes)
> 4( 4 mod 256): FALLOC 0x53c38 thru 0x5e853 (0xac1b bytes) INTERIOR
> 5( 5 mod 256): COPY 0x55000 thru 0x59fff (0x5000 bytes) to 0x25000 thru 0x29fff
> 6( 6 mod 256): WRITE 0x74000 thru 0x88fff (0x15000 bytes)
> 7( 7 mod 256): ZERO 0xedb1 thru 0x11693 (0x28e3 bytes)
>
> with a warning in dmesg from iomap about XFS trying to give it a
> delalloc mapping for a directio write. Fix the software atomic write
> iomap_begin code to convert the reservation into a written mapping.
> This doesn't fix the data corruption problems reported by generic/760,
> but it's a start.
>
> Cc: stable@vger.kernel.org # v6.16
> Fixes: bd1d2c21d5d249 ("xfs: add xfs_atomic_write_cow_iomap_begin()")
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> Reviewed-by: John Garry <john.g.garry@oracle.com>
> Signed-off-by: Carlos Maiolino <cem@kernel.org>
> Stable-dep-of: 8d7bba1e8314 ("xfs: fix various problems in xfs_atomic_write_cow_iomap_begin")
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> fs/xfs/xfs_iomap.c | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
> index 2a74f29573410..a4a22975c7cc9 100644
> --- a/fs/xfs/xfs_iomap.c
> +++ b/fs/xfs/xfs_iomap.c
> @@ -1121,7 +1121,7 @@ xfs_atomic_write_cow_iomap_begin(
> return -EAGAIN;
>
> trace_xfs_iomap_atomic_write_cow(ip, offset, length);
> -
> +retry:
> xfs_ilock(ip, XFS_ILOCK_EXCL);
>
> if (!ip->i_cowfp) {
> @@ -1132,6 +1132,8 @@ xfs_atomic_write_cow_iomap_begin(
> if (!xfs_iext_lookup_extent(ip, ip->i_cowfp, offset_fsb, &icur, &cmap))
> cmap.br_startoff = end_fsb;
> if (cmap.br_startoff <= offset_fsb) {
> + if (isnullstartblock(cmap.br_startblock))
> + goto convert_delay;
> xfs_trim_extent(&cmap, offset_fsb, count_fsb);
> goto found;
> }
> @@ -1160,8 +1162,10 @@ xfs_atomic_write_cow_iomap_begin(
> if (!xfs_iext_lookup_extent(ip, ip->i_cowfp, offset_fsb, &icur, &cmap))
> cmap.br_startoff = end_fsb;
> if (cmap.br_startoff <= offset_fsb) {
> - xfs_trim_extent(&cmap, offset_fsb, count_fsb);
> xfs_trans_cancel(tp);
> + if (isnullstartblock(cmap.br_startblock))
> + goto convert_delay;
> + xfs_trim_extent(&cmap, offset_fsb, count_fsb);
> goto found;
> }
>
> @@ -1201,6 +1205,19 @@ xfs_atomic_write_cow_iomap_begin(
> xfs_iunlock(ip, XFS_ILOCK_EXCL);
> return xfs_bmbt_to_iomap(ip, iomap, &cmap, flags, IOMAP_F_SHARED, seq);
>
> +convert_delay:
> + xfs_iunlock(ip, XFS_ILOCK_EXCL);
> + error = xfs_bmapi_convert_delalloc(ip, XFS_COW_FORK, offset, iomap,
> + NULL);
> + if (error)
> + return error;
> +
> + /*
> + * Try the lookup again, because the delalloc conversion might have
> + * turned the COW mapping into unwritten, but we need it to be in
> + * written state.
> + */
> + goto retry;
> out_unlock:
> xfs_iunlock(ip, XFS_ILOCK_EXCL);
> return error;
> --
> 2.51.0
>
>
Did not apply to 6.17.y at all :(
prev parent reply other threads:[~2025-11-21 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 3:11 FAILED: patch "[PATCH] xfs: fix various problems in xfs_atomic_write_cow_iomap_begin" failed to apply to 6.17-stable tree gregkh
2025-11-09 23:20 ` [PATCH 6.17.y 1/2] xfs: fix delalloc write failures in software-provided atomic writes Sasha Levin
2025-11-09 23:20 ` [PATCH 6.17.y 2/2] xfs: fix various problems in xfs_atomic_write_cow_iomap_begin Sasha Levin
2025-11-21 9:47 ` Greg KH
2025-11-24 15:25 ` Sasha Levin
2025-11-21 9:47 ` Greg KH [this message]
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=2025112133-bleak-stamina-42ba@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=sashal@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.