From: Keith Busch <kbusch@kernel.org>
To: Yang Xiuwei <yangxiuwei@kylinos.cn>
Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed()
Date: Tue, 28 Jul 2026 15:07:50 -0600 [thread overview]
Message-ID: <amkaJgFRImL888VT@kbusch-mbp> (raw)
In-Reply-To: <20260720060305.885535-1-yangxiuwei@kylinos.cn>
On Mon, Jul 20, 2026 at 02:03:05PM +0800, Yang Xiuwei wrote:
> Unlike IO_CMD / IO64_CMD, NVME_IOCTL_SUBMIT_IO never calls
> nvme_cmd_allowed(). Unprivileged callers can thus issue I/O on a
> partition device or write through a read-only file descriptor.
Thanks, applied to nvme-7.3.
prev parent reply other threads:[~2026-07-28 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 6:03 [PATCH] nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() Yang Xiuwei
2026-07-20 8:06 ` Christoph Hellwig
2026-07-28 21:07 ` 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=amkaJgFRImL888VT@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=yangxiuwei@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 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.