From: Yi Zhang <yi.zhang@redhat.com>
To: shinichiro.kawasaki@wdc.com, chaitanyak@nvidia.com
Cc: linux-block@vger.kernel.org
Subject: [PATCH blktests 0/3] fix for xfs log size change from new version of xfsprogs
Date: Mon, 24 Oct 2022 14:13:16 +0800 [thread overview]
Message-ID: <20221024061319.1133470-1-yi.zhang@redhat.com> (raw)
Hi
This first patch addressed nvme/012 nvme/013 failure which introduced from xfsprogs
v5.19.0, the minimum xfs log size changed to 64m.
The second patch introduced one new function _get_test_dev_size_mb.
The third patch updated _xfs_run_fio_verify_io to accept one new
parameter size which will be used for nvme/012 nvme/013 nvme/015
Yi Zhang (3):
common/xfs: set the minimal log size 64m during mkfs.xfs
common/rc: add one function to get test dev size in mb
common/xfs: update _xfs_run_fio_verify_io to accept the size parameter
common/rc | 8 ++++++++
common/xfs | 5 +++--
tests/nvme/012 | 2 +-
tests/nvme/013 | 2 +-
tests/nvme/035 | 9 ++++++++-
5 files changed, 21 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2022-10-24 6:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 6:13 Yi Zhang [this message]
2022-10-24 6:13 ` [PATCH blktests 1/3] common/xfs: set the minimal log size 64m during mkfs.xfs Yi Zhang
2022-10-24 6:13 ` [PATCH blktests 2/3] common/rc: add one function to get test dev size in mb Yi Zhang
2022-10-25 2:29 ` Shinichiro Kawasaki
2022-11-02 3:01 ` Yi Zhang
2022-10-24 6:13 ` [PATCH blktests 3/3] common/xfs: update _xfs_run_fio_verify_io to accept the size parameter Yi Zhang
2022-10-25 2:49 ` Shinichiro Kawasaki
2022-11-02 3:04 ` Yi Zhang
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=20221024061319.1133470-1-yi.zhang@redhat.com \
--to=yi.zhang@redhat.com \
--cc=chaitanyak@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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 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.