From: Keith Busch <kbusch@kernel.org>
To: Yao Sang <sangyao@kylinos.cn>
Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org,
Kanchan Joshi <joshi.k@samsung.com>
Subject: Re: [PATCH v2] nvme: pass partition flags to passthrough checks
Date: Tue, 13 Oct 2026 09:44:58 -0600 [thread overview]
Message-ID: <as5R-unUet33avke@kbusch-mbp> (raw)
In-Reply-To: <20261013075324.565535-1-sangyao@kylinos.cn>
On Tue, Oct 13, 2026 at 03:53:24PM +0800, Yao Sang wrote:
> nvme_user_cmd() handles NVME_IOCTL_IO_CMD on namespace block devices,
> including partitions. It receives flags identifying a partition, but
> passes 0 to nvme_cmd_allowed(), bypassing the partition guard and
> allowing unprivileged passthrough commands to access sectors outside
> the partition.
>
> Pass flags to the permission check, rejecting unprivileged commands on
> partitions.
Thanks, applied to nvme-7.4.
prev parent reply other threads:[~2026-10-13 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 7:53 [PATCH v2] nvme: pass partition flags to passthrough checks Yao Sang
2026-10-13 14:20 ` Christoph Hellwig
2026-10-13 15:44 ` Keith Busch [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=as5R-unUet33avke@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=joshi.k@samsung.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sangyao@kylinos.cn \
/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