io_uring: fail NOP if non-zero op flags is passed in

BugLink: https://bugs.launchpad.net/bugs/2071621

commit 3d8f874bd620ce03f75a5512847586828ab86544 upstream.

The NOP op flags should have been checked from beginning like any other
opcode, otherwise NOP may not be extended with the op flags.

Given both liburing and Rust io-uring crate always zeros SQE op flags, just
ignore users which play raw NOP uring interface without zeroing SQE, because
NOP is just for test purpose. Then we can save one NOP2 opcode.

Suggested-by: Jens Axboe <axboe@kernel.dk>
Fixes: 2b188cc1bb ("Add io_uring IO interface")
Cc: stable@vger.kernel.org
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Link: https://lore.kernel.org/r/20240510035031.78874-2-ming.lei@redhat.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Manuel Diewald <manuel.diewald@canonical.com>
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>

This commit is contained in:

Ming Lei

2024-05-10 11:50:27 +08:00

committed by

Stefan Bader

parent 55de1fa464

commit 9d3ab2045b

1 changed files with 2 additions and 0 deletions

									
										io_uring/nop.c
									
		+2
		
												View File
												
				@@ -12,6 +12,8 @@

				int io_nop_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)

				{

					if (READ_ONCE(sqe->rw_flags))

						return -EINVAL;

					return 0;

				}