From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: hch@lst.de, kbusch@kernel.org, axboe@kernel.dk, sagi@grimberg.me,
chaitanyak@nvidia.com, linux-nvme@lists.infradead.org,
gost.dev@samsung.com
Subject: Re: [PATCH v4 0/2] Granular CAP_SYS_ADMIN
Date: Tue, 1 Nov 2022 10:44:54 +0100 [thread overview]
Message-ID: <20221101094454.GA12839@lst.de> (raw)
In-Reply-To: <20221031162351.31856-1-joshi.k@samsung.com>
Thanks,
I've applied this to nvme-6.2, and I've also extended the comments
explaining the checks in nvme_cmd_allowed a bit.
prev parent reply other threads:[~2022-11-01 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221031163523epcas5p327b516ddab691c02d2e3ad2a80a7bdce@epcas5p3.samsung.com>
2022-10-31 16:23 ` [PATCH v4 0/2] Granular CAP_SYS_ADMIN Kanchan Joshi
2022-10-31 16:23 ` [PATCH v4 1/2] nvme: fine-granular CAP_SYS_ADMIN for nvme io commands Kanchan Joshi
2022-10-31 16:23 ` [PATCH v4 2/2] nvme: identify-namespace without CAP_SYS_ADMIN Kanchan Joshi
2022-11-01 2:35 ` [PATCH v4 0/2] Granular CAP_SYS_ADMIN Chaitanya Kulkarni
2022-11-01 9:44 ` Christoph Hellwig [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=20221101094454.GA12839@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=gost.dev@samsung.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.