From: Ziyang Zhang <ZiyangZhang@linux.alibaba.com>
To: shinichiro.kawasaki@wdc.com, ming.lei@redhat.com
Cc: linux-block@vger.kernel.org,
Ziyang Zhang <ZiyangZhang@linux.alibaba.com>
Subject: [PATCH blktests 0/2] blktests: Add ublk testcases
Date: Thu, 27 Apr 2023 18:32:40 +0800 [thread overview]
Message-ID: <20230427103242.31361-1-ZiyangZhang@linux.alibaba.com> (raw)
Hi,
ublk can passthrough I/O requests to userspce daemons. It is very important
to test ublk crash handling since the userspace part is not reliable.
Especially we should test removing device, killing ublk daemons and user
recovery feature.
The first patch add user recovery support in miniublk.
The second patch add five new tests for ublk to cover above cases.
Ziyang Zhang (2):
src/miniublk: add user recovery
tests: Add ublk tests
src/miniublk.c | 207 +++++++++++++++++++++++++++++++++++++++++++--
tests/ublk/001 | 39 +++++++++
tests/ublk/001.out | 2 +
tests/ublk/002 | 53 ++++++++++++
tests/ublk/002.out | 2 +
tests/ublk/003 | 43 ++++++++++
tests/ublk/003.out | 2 +
tests/ublk/004 | 63 ++++++++++++++
tests/ublk/004.out | 2 +
tests/ublk/005 | 66 +++++++++++++++
tests/ublk/005.out | 2 +
11 files changed, 472 insertions(+), 9 deletions(-)
create mode 100644 tests/ublk/001
create mode 100644 tests/ublk/001.out
create mode 100644 tests/ublk/002
create mode 100644 tests/ublk/002.out
create mode 100644 tests/ublk/003
create mode 100644 tests/ublk/003.out
create mode 100644 tests/ublk/004
create mode 100644 tests/ublk/004.out
create mode 100644 tests/ublk/005
create mode 100644 tests/ublk/005.out
--
2.31.1
next reply other threads:[~2023-04-27 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 10:32 Ziyang Zhang [this message]
2023-04-27 10:32 ` [PATCH blktests 1/2] src/miniublk: add user recovery Ziyang Zhang
2023-04-27 10:46 ` Chaitanya Kulkarni
2023-04-28 2:16 ` Ming Lei
2023-04-27 10:32 ` [PATCH blktests 2/2] tests: Add ublk tests Ziyang Zhang
2023-04-28 3:10 ` Ming Lei
2023-05-01 9:15 ` Shinichiro Kawasaki
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=20230427103242.31361-1-ZiyangZhang@linux.alibaba.com \
--to=ziyangzhang@linux.alibaba.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox