From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH v2 1/6] io_uring: fortify io_pin_pages with a warning
Date: Thu, 14 Nov 2024 17:38:31 +0000 [thread overview]
Message-ID: <d48e0c097cbd90fb47acaddb6c247596510d8cfc.1731604990.git.asml.silence@gmail.com> (raw)
In-Reply-To: <[email protected]>
We're a bit too frivolous with types of nr_pages arguments, converting
it to long and back to int, passing an unsigned int pointer as an int
pointer and so on. Shouldn't cause any problem but should be carefully
reviewed, but until then let's add a WARN_ON_ONCE check to be more
confident callers don't pass poorely checked arguents.
Signed-off-by: Pavel Begunkov <[email protected]>
---
io_uring/memmap.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/io_uring/memmap.c b/io_uring/memmap.c
index 85c66fa54956..6ab59c60dfd0 100644
--- a/io_uring/memmap.c
+++ b/io_uring/memmap.c
@@ -140,6 +140,8 @@ struct page **io_pin_pages(unsigned long uaddr, unsigned long len, int *npages)
nr_pages = end - start;
if (WARN_ON_ONCE(!nr_pages))
return ERR_PTR(-EINVAL);
+ if (WARN_ON_ONCE(nr_pages > INT_MAX))
+ return ERR_PTR(-EOVERFLOW);
pages = kvmalloc_array(nr_pages, sizeof(struct page *), GFP_KERNEL);
if (!pages)
--
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 ` Pavel Begunkov [this message]
2024-11-14 17:38 ` [PATCH v2 2/6] io_uring: disable ENTER_EXT_ARG_REG for IOPOLL Pavel Begunkov
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=d48e0c097cbd90fb47acaddb6c247596510d8cfc.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