From: Jens Axboe <axboe@kernel.dk>
To: Subramanya Swamy <subramanya.swamy.linux@gmail.com>,
corbet@lwn.net, jmoyer@redhat.com, asml.silence@gmail.com,
akpm@linux-foundation.org, bhe@redhat.com, ribalda@chromium.org,
rostedt@goodmis.org, sshegde@linux.vnet.ibm.com,
alexghiti@rivosinc.com, matteorizzo@google.com, ardb@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
io-uring@vger.kernel.org
Subject: Re: [PATCH v2] iouring:added boundary value check for io_uring_group systl
Date: Sat, 20 Jan 2024 10:01:51 -0700 [thread overview]
Message-ID: <f48e47b5-0572-4f84-b165-5a9e91788c57@kernel.dk> (raw)
In-Reply-To: <20240120144411.2564-1-subramanya.swamy.linux@gmail.com>
On 1/20/24 7:44 AM, Subramanya Swamy wrote:
> /proc/sys/kernel/io_uring_group takes gid as input
> added boundary value check to accept gid in range of
> 0<=gid<=4294967294 & Documentation is updated for same
This should have:
Fixes: 76d3ccecfa18 ("io_uring: add a sysctl to disable io_uring system-wide")
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index 6584a1f9bfe3..a8b61ab3e118 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -470,10 +470,8 @@ io_uring_group
> ==============
>
> When io_uring_disabled is set to 1, a process must either be
> -privileged (CAP_SYS_ADMIN) or be in the io_uring_group group in order
> -to create an io_uring instance. If io_uring_group is set to -1 (the
> -default), only processes with the CAP_SYS_ADMIN capability may create
> -io_uring instances.
> +privledged (CAP_SYS_ADMIN) or be in the io_uring_group group in order
privileged.
--
Jens Axboe
next prev parent reply other threads:[~2024-01-20 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 14:44 Subramanya Swamy
2024-01-20 17:01 ` Jens Axboe [this message]
2024-01-20 18:19 ` Subramanya Swamy
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=f48e47b5-0572-4f84-b165-5a9e91788c57@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=ardb@kernel.org \
--cc=asml.silence@gmail.com \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=io-uring@vger.kernel.org \
--cc=jmoyer@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matteorizzo@google.com \
--cc=ribalda@chromium.org \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.vnet.ibm.com \
--cc=subramanya.swamy.linux@gmail.com \
/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
all inboxes | Powered by JetHome®