diff options
| author | Caleb Sander Mateos <csander@purestorage.com> | 2025-03-28 18:46:45 +0300 |
|---|---|---|
| committer | Keith Busch <kbusch@kernel.org> | 2025-04-01 19:01:05 +0300 |
| commit | eada75467fca0b016b9b22212637c07216135c20 (patch) | |
| tree | 454702cd13c7e244853bf8b39132432c6ec6eb03 /tools/perf/scripts/python/arm-cs-trace-disasm.py | |
| parent | ea7789c1541084a3dae65ffd36778348dd98f61b (diff) | |
| download | linux-eada75467fca0b016b9b22212637c07216135c20.tar.xz | |
nvme/ioctl: don't warn on vectorized uring_cmd with fixed buffer
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>
Diffstat (limited to 'tools/perf/scripts/python/arm-cs-trace-disasm.py')
0 files changed, 0 insertions, 0 deletions