From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH v2 2/6] io_uring: disable ENTER_EXT_ARG_REG for IOPOLL
Date: Thu, 14 Nov 2024 17:38:32 +0000 [thread overview]
Message-ID: <a35ecd919dbdc17bd5b7932273e317832c531b45.1731604990.git.asml.silence@gmail.com> (raw)
In-Reply-To: <[email protected]>
IOPOLL doesn't use the extended arguments, no need for it to support
IORING_ENTER_EXT_ARG_REG. Let's disable it for IOPOLL, if anything it
leaves more space for future extensions.
Signed-off-by: Pavel Begunkov <[email protected]>
---
io_uring/io_uring.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
index bd71782057de..464a70bde7e6 100644
--- a/io_uring/io_uring.c
+++ b/io_uring/io_uring.c
@@ -3214,12 +3214,8 @@ static int io_validate_ext_arg(struct io_ring_ctx *ctx, unsigned flags,
if (!(flags & IORING_ENTER_EXT_ARG))
return 0;
-
- if (flags & IORING_ENTER_EXT_ARG_REG) {
- if (argsz != sizeof(struct io_uring_reg_wait))
- return -EINVAL;
- return PTR_ERR(io_get_ext_arg_reg(ctx, argp));
- }
+ if (flags & IORING_ENTER_EXT_ARG_REG)
+ return -EINVAL;
if (argsz != sizeof(arg))
return -EINVAL;
if (copy_from_user(&arg, argp, sizeof(arg)))
--
2.46.0
next prev parent reply other threads:[~2024-11-14 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 17:38 [PATCH v2 0/6] regions, param pre-mapping and reg waits extension Pavel Begunkov
2024-11-14 17:38 ` [PATCH v2 1/6] io_uring: fortify io_pin_pages with a warning Pavel Begunkov
2024-11-14 17:38 ` Pavel Begunkov [this message]
2024-11-14 17:38 ` [PATCH v2 3/6] io_uring: temporarily disable registered waits Pavel Begunkov
2024-11-14 17:38 ` [PATCH v2 4/6] io_uring: introduce concept of memory regions Pavel Begunkov
2024-11-14 17:38 ` [PATCH v2 5/6] io_uring: add memory region registration Pavel Begunkov
2024-11-14 17:38 ` [PATCH v2 6/6] io_uring: restore back registered wait arguments Pavel Begunkov
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=a35ecd919dbdc17bd5b7932273e317832c531b45.1731604990.git.asml.silence@gmail.com \
[email protected] \
[email protected] \
/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