From: Jens Axboe <axboe@kernel.dk>
To: matteorizzo@google.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, io-uring@vger.kernel.org,
asml.silence@gmail.com, Jeff Moyer <jmoyer@redhat.com>
Cc: corbet@lwn.net, akpm@linux-foundation.org, keescook@chromium.org,
ribalda@chromium.org, rostedt@goodmis.org, jannh@google.com,
chenhuacai@kernel.org, gpiccoli@igalia.com,
ldufour@linux.ibm.com, evn@google.com, poprdi@google.com,
jordyzomer@google.com, krisman@suse.de, andres@anarazel.de
Subject: Re: [PATCH v5] io_uring: add a sysctl to disable io_uring system-wide
Date: Tue, 05 Sep 2023 08:44:12 -0600 [thread overview]
Message-ID: <169392505265.592530.1699660694804027481.b4-ty@kernel.dk> (raw)
In-Reply-To: <x49y1i42j1z.fsf@segfault.boston.devel.redhat.com>
On Mon, 21 Aug 2023 17:15:52 -0400, Jeff Moyer wrote:
> Introduce a new sysctl (io_uring_disabled) which can be either 0, 1, or
> 2. When 0 (the default), all processes are allowed to create io_uring
> instances, which is the current behavior. When 1, io_uring creation is
> disabled (io_uring_setup() will fail with -EPERM) for unprivileged
> processes not in the kernel.io_uring_group group. When 2, calls to
> io_uring_setup() fail with -EPERM regardless of privilege.
>
> [...]
Applied, thanks!
[1/1] io_uring: add a sysctl to disable io_uring system-wide
commit: 76d3ccecfa186af3120e206d62f03db1a94a535f
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-09-05 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 21:15 Jeff Moyer
2023-09-05 14:24 ` Matteo Rizzo
2023-09-05 14:43 ` Jens Axboe
2023-09-05 14:44 ` Jens Axboe [this message]
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=169392505265.592530.1699660694804027481.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=andres@anarazel.de \
--cc=asml.silence@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=evn@google.com \
--cc=gpiccoli@igalia.com \
--cc=io-uring@vger.kernel.org \
--cc=jannh@google.com \
--cc=jmoyer@redhat.com \
--cc=jordyzomer@google.com \
--cc=keescook@chromium.org \
--cc=krisman@suse.de \
--cc=ldufour@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matteorizzo@google.com \
--cc=poprdi@google.com \
--cc=ribalda@chromium.org \
--cc=rostedt@goodmis.org \
/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®