]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
nvme/ioctl: don't warn on vectorized uring_cmd with fixed buffer
authorCaleb Sander Mateos <csander@purestorage.com>
Fri, 28 Mar 2025 15:46:45 +0000 (09:46 -0600)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 10 Apr 2025 12:39:33 +0000 (14:39 +0200)
commita3800b64f866c06c1f631de91a7e82880b8780eb
treec561d4ec2d51b26ccac90d44b70bfe434534fd36
parentc35ec5e046ba5c0e410eb3a99771e691ea093170
nvme/ioctl: don't warn on vectorized uring_cmd with fixed buffer

[ Upstream commit eada75467fca0b016b9b22212637c07216135c20 ]

The vectorized io_uring NVMe passthru opcodes don't yet support fixed
buffers. But since userspace can trigger this condition based on the
io_uring SQE parameters, it shouldn't cause a kernel warning.

Signed-off-by: Caleb Sander Mateos <csander@purestorage.com>
Reviewed-by: Jens Axboe <axboe@kernel.dk>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Fixes: 23fd22e55b76 ("nvme: wire up fixed buffer support for nvme passthrough")
Signed-off-by: Keith Busch <kbusch@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/nvme/host/ioctl.c