linux-unionfs mirror
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-unionfs@vger.kernel.org, io-uring@vger.kernel.org,
	fstests@vger.kernel.org
Subject: Re: [xfstests generic/617] fsx io_uring dio starts to fail on overlayfs since v6.6-rc1
Date: Mon, 25 Sep 2023 14:35:30 +0800	[thread overview]
Message-ID: <20230925063530.m4wpinakby26b6q5@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com> (raw)
In-Reply-To: <02c1c68c-61a0-4d93-8619-971c0416b0e6@kernel.dk>

On Sun, Sep 24, 2023 at 11:52:12AM -0600, Jens Axboe wrote:
> On 9/24/23 8:29 AM, Zorro Lang wrote:
> > Hi,
> > 
> > The generic/617 of fstests is a test case does IO_URING soak direct-IO
> > fsx test, but recently (about from v6.6-rc1 to now) it always fails on
> > overlayfs as [1], no matter the underlying fs is ext4 or xfs. But it
> > never failed on overlay before, likes [2].
> > 
> > So I thought it might be a regression of overlay or io-uring on current v6.6.
> > Please help to review, it's easy to reproduce. My system is Fedora-rawhide/RHEL-9,
> > with upstream mainline linux HEAD=dc912ba91b7e2fa74650a0fc22cccf0e0d50f371.
> > The generic/617.full output as [3].
> 
> It works without overlayfs - would be great if you could include how to
> reproduce this with overlayfs.

Sorry I didn't provide the test steps:

1) git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
2) cd xfstests-dev
3) make -j8  # refer to README, about how to build xfstests
4) vi local.config
# The FSTYP can be other fs, e.g. ext4.
# The TEST_DEV and SCRATCH_DEV can be any local devices you have (even loopdev)
# TEST_DIR and SCRATCH_MNT can be changed too
export FSTYP=xfs
export TEST_DEV=/dev/sda5
export TEST_DIR=/mnt/test
export SCRATCH_DEV=/dev/sda3
export SCRATCH_MNT=/mnt/scratch

5) mkfs.xfs -f /dev/sda5 && mkfs.xfs -f /dev/sda3
6) mkdir -p /mnt/test && mkdir -p /mnt/scratch
7) ./check -overlay generic/617

The step#6 will be failed.

Thanks,
Zorro

> 
> -- 
> Jens Axboe
> 


      parent reply	other threads:[~2023-09-25  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 14:29 [xfstests generic/617] fsx io_uring dio starts to fail on overlayfs since v6.6-rc1 Zorro Lang
2023-09-24 15:45 ` Amir Goldstein
2023-09-24 17:52 ` Jens Axboe
2023-09-24 19:16   ` Jens Axboe
2023-09-25  6:35   ` Zorro Lang [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=20230925063530.m4wpinakby26b6q5@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com \
    --to=zlang@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=fstests@vger.kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-unionfs@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 read-only IMAP folder(s) and NNTP newsgroup(s).