From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Kanchan Joshi <joshi.k@samsung.com>
Cc: Christoph Hellwig <hch@lst.de>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [PATCH blktests v2 0/2] nvme: add test for unprivileged passthrough
Date: Tue, 14 Feb 2023 13:47:37 +0900 [thread overview]
Message-ID: <20230214044739.1903364-1-shinichiro.kawasaki@wdc.com> (raw)
Per suggestion by Kanchan, add a new test case to test unprivileged passthrough
of NVME character devices. The first patch adds a feature to run commands with
normal user privilege. The second patch adds the test case using the feature.
Changes from v2:
* Added the first patch to add normal user privilege support to blktests
* Adjusted the test case to the functions for normal user privilege support
Kanchan Joshi (1):
nvme/046: add test for unprivileged passthrough
Shin'ichiro Kawasaki (1):
check, common/rc: support normal user privilege
Documentation/running-tests.md | 10 +++++++
check | 1 +
common/rc | 13 +++++++++
tests/nvme/046 | 50 ++++++++++++++++++++++++++++++++++
tests/nvme/046.out | 2 ++
5 files changed, 76 insertions(+)
create mode 100644 tests/nvme/046
create mode 100644 tests/nvme/046.out
--
2.38.1
next reply other threads:[~2023-02-14 4:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230214044749epcas5p4ac6bf441e046e3642b1633fd9cf7a72b@epcas5p4.samsung.com>
2023-02-14 4:47 ` Shin'ichiro Kawasaki [this message]
2023-02-14 4:47 ` [PATCH blktests v2 1/2] check, common/rc: support normal user privilege Shin'ichiro Kawasaki
2023-02-14 4:47 ` [PATCH blktests v2 2/2] nvme/046: add test for unprivileged passthrough Shin'ichiro Kawasaki
2023-02-27 6:05 ` [PATCH blktests v2 0/2] nvme: " Kanchan Joshi
2023-02-27 11:24 ` Shinichiro Kawasaki
2023-02-27 14:18 ` Kanchan Joshi
2023-02-28 4:07 ` 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=20230214044739.1903364-1-shinichiro.kawasaki@wdc.com \
--to=shinichiro.kawasaki@wdc.com \
--cc=hch@lst.de \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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 NNTP newsgroup(s).