From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH blktests v2 0/2] nvme: add test for unprivileged passthrough
Date: Tue, 28 Feb 2023 04:07:04 +0000 [thread overview]
Message-ID: <20230228040703.5zqrhf3d7s3choss@shindev> (raw)
In-Reply-To: <20230227141802.GA27506@green5>
On Feb 27, 2023 / 19:48, Kanchan Joshi wrote:
> On Mon, Feb 27, 2023 at 11:24:04AM +0000, Shinichiro Kawasaki wrote:
> > On Feb 27, 2023 / 11:35, Kanchan Joshi wrote:
> > > On Tue, Feb 14, 2023 at 01:47:37PM +0900, Shin'ichiro Kawasaki wrote:
> > > > 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
> > >
> > > Thanks, this looks way better. And works fine in my setup.
> > > If required,
> > > Tested-by: Kanchan Joshi <joshi.k@samsung.com>
> >
> > Thanks for the confirmation. Sounds good.
> >
> > I found two more minor points to improve:
> >
> > 1) tests/nvme/046 does not have executable mode bit. I will add it when I apply
> > the patch.
> >
> > 2) I ran the test case with kernel version v6.1 and it failed. Does the test
> > case require kernel version 6.2 or higher? If that is the case, one more line
> > change will be required as follows. If you are ok with the change, I can fold
> > this change in when I apply the patches.
>
> Yes, unprivileged passthrough exists from 6.2. Changes looks good.
> Thanks.
All right, I've applied the patches. Thanks!
--
Shin'ichiro Kawasaki
prev parent reply other threads:[~2023-02-28 4:07 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 ` [PATCH blktests v2 0/2] nvme: add test for unprivileged passthrough Shin'ichiro Kawasaki
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 [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=20230228040703.5zqrhf3d7s3choss@shindev \
--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