public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 209243] [regression] fsx IO_URING reading get BAD DATA
Date: Mon, 14 Sep 2020 15:04:05 +0000	[thread overview]
Message-ID: <bug-209243-201763-mnIvMSU3Bb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209243-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209243

--- Comment #7 from Zorro Lang (zlang@redhat.com) ---
(In reply to Jens Axboe from comment #6)
> I'll take a look. Do you have a repo of fsstress with your io_uring changes
> included?

Thanks for your reply. Sorry, I don't prepare a public xfstests git repo. But
you can:

1) git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
2) merget below 5 patches into above xfstests:
https://patchwork.kernel.org/patch/11769857/
https://patchwork.kernel.org/patch/11769849/
https://patchwork.kernel.org/patch/11769851/
https://patchwork.kernel.org/patch/11769853/
https://patchwork.kernel.org/patch/11769855/

3) build xfstests with liburing install
4) make a XFS filesystem on a LVM device
5) mount the xfs filesystem
6) run xfstests/ltp/fsx -U -R -W -o 128000 $mnt/foo

Thanks,
Zorro

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-09-14 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12  5:46 [Bug 209243] New: fsx IO_URING reading get BAD DATA bugzilla-daemon
2020-09-12  5:50 ` [Bug 209243] " bugzilla-daemon
2020-09-13  7:59 ` bugzilla-daemon
2020-09-13 15:00 ` bugzilla-daemon
2020-09-13 18:05 ` bugzilla-daemon
2020-09-14  7:07 ` [Bug 209243] [regression] " bugzilla-daemon
2020-09-14 13:39 ` bugzilla-daemon
2020-09-14 15:04 ` bugzilla-daemon [this message]
2020-09-14 15:27 ` bugzilla-daemon
2020-09-14 18:17 ` bugzilla-daemon
2020-09-14 19:49 ` bugzilla-daemon

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=bug-209243-201763-mnIvMSU3Bb@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@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