From: "Pankaj Raghav (Samsung)" <pankaj.raghav@linux.dev>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] iomap: only follow dio alignment requirement if specified
Date: Mon, 26 Oct 2026 15:21:24 +0100 [thread overview]
Message-ID: <at9hcoPC5NnKADX3@quentin> (raw)
In-Reply-To: <9fae60fcce5ae356deef5e38931124b9634dba3b.1792997261.git.wqu@suse.com>
Hi Qu,
On Mon, Oct 26, 2026 at 05:18:13PM +1030, Qu Wenruo wrote:
> [BUG]
> After commit 4025185cf953 ("iomap: follow the alignment requirement for
> iomap_dio_hole_iter()"), generic/091 fails on both xfs and ext4:
>
> FSTYP -- ext4
> PLATFORM -- Linux/x86_64 btrfs-vm 7.3.0-custom+ #6 SMP PREEMPT_DYNAMIC Mon Oct 26 16:04:56 ACDT 2026
> MKFS_OPTIONS -- -F /dev/mapper/test-scratch1
> MOUNT_OPTIONS -- -o acl,user_xattr /dev/mapper/test-scratch1 /mnt/scratch
>
> generic/091 6s ... [failed, exit status 1]- output mismatch (see /home/adam/xfstests/results//generic/091.out.bad)
> --- /home/adam/xfstests/tests/generic/091.out 2022-05-11 11:25:30.766666664 +0930
> +++ /home/adam/xfstests/results//generic/091.out.bad 2026-10-26 16:43:49.387401669 +1030
> @@ -1,7 +1,25 @@
> QA output created by 091
> fsx -N 10000 -l 500000 -r PSIZE -t BSIZE -w BSIZE -Z -R -W
> -fsx -N 10000 -o 8192 -l 500000 -r PSIZE -t BSIZE -w BSIZE -Z -R -W
> -fsx -N 10000 -o 32768 -l 500000 -r PSIZE -t BSIZE -w BSIZE -Z -R -W
> -fsx -N 10000 -o 8192 -l 500000 -r PSIZE -t BSIZE -w BSIZE -Z -R -W
> -fsx -N 10000 -o 32768 -l 500000 -r PSIZE -t BSIZE -w BSIZE -Z -R -W
> -fsx -N 10000 -o 128000 -l 500000 -r PSIZE -t BSIZE -w BSIZE -Z -W
> ...
> (Run 'diff -u /home/adam/xfstests/tests/generic/091.out /home/adam/xfstests/results//generic/091.out.bad' to see the entire diff)
> Ran: generic/091
> Failures: generic/091
> Failed 1 of 1 tests
>
I am trying to reproduce this error in fs-next with ext4/xfs but I am unable
to.
Do we need some specific disk setup or xfstests config to trigger this?
> [CAUSE]
> The failed command of fsx is COPY_RANGE:
>
> copy range: 0x6800 to 0xa200 at 0x3f200
--
Pankaj
next prev parent reply other threads:[~2026-10-26 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 6:48 [PATCH] iomap: only follow dio alignment requirement if specified Qu Wenruo
2026-10-26 14:21 ` Pankaj Raghav (Samsung) [this message]
2026-10-26 19:49 ` Pankaj Raghav (Samsung)
2026-10-26 20:59 ` Qu Wenruo
2026-10-26 21:29 ` Qu Wenruo
2026-10-27 10:07 ` Pankaj Raghav
2026-10-27 10:12 ` Qu Wenruo
2026-10-27 11:14 ` Pankaj Raghav
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=at9hcoPC5NnKADX3@quentin \
--to=pankaj.raghav@linux.dev \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wqu@suse.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