From: Jeff Moyer <jmoyer@redhat.com>
To: Matteo Rizzo <matteorizzo@google.com>
Cc: Ricardo Ribalda <ribalda@chromium.org>,
Bart Van Assche <bvanassche@acm.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
io-uring@vger.kernel.org, jordyzomer@google.com, evn@google.com,
poprdi@google.com, corbet@lwn.net, axboe@kernel.dk,
asml.silence@gmail.com, akpm@linux-foundation.org,
keescook@chromium.org, rostedt@goodmis.org,
dave.hansen@linux.intel.com, chenhuacai@kernel.org,
steve@sk2.org, gpiccoli@igalia.com, ldufour@linux.ibm.com
Subject: Re: [PATCH 1/1] Add a new sysctl to disable io_uring system-wide
Date: Wed, 28 Jun 2023 11:59:56 -0400 [thread overview]
Message-ID: <x497crnefwj.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <CAHKB1w+UyOnC_rOBABVhmzG+XeePaWYgPJWxX9NUeqnAi9WcgA@mail.gmail.com> (Matteo Rizzo's message of "Wed, 28 Jun 2023 17:12:42 +0200")
Matteo Rizzo <matteorizzo@google.com> writes:
> On Wed, 28 Jun 2023 at 13:44, Ricardo Ribalda <ribalda@chromium.org> wrote:
>>
>> Have you considered that the new sysctl is "sticky like kexec_load_disabled.
>> When the user disables it there is no way to turn it back on until the
>> system is rebooted.
>
> Are you suggesting making this sysctl sticky? Are there any examples of how to
> implement a sticky sysctl that can take more than 2 values in case we want to
> add an intermediate level that still allows privileged processes to use
> io_uring? Also, what would be the use case? Preventing privileged processes
> from re-enabling io_uring?
See unprivileged_bpf_disabled for an example. I can't speak to the use
case for a sticky value.
-Jeff
next prev parent reply other threads:[~2023-06-28 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 12:00 [PATCH 0/1] Add a " Matteo Rizzo
2023-06-27 12:00 ` [PATCH 1/1] Add a new " Matteo Rizzo
2023-06-27 16:23 ` Randy Dunlap
2023-06-27 17:10 ` Bart Van Assche
2023-06-27 18:15 ` Matteo Rizzo
2023-06-28 11:36 ` Ricardo Ribalda
2023-06-28 15:12 ` Matteo Rizzo
2023-06-28 15:59 ` Jeff Moyer [this message]
2023-06-28 15:59 ` Ricardo Ribalda
2023-06-28 13:50 ` Gabriel Krisman Bertazi
2023-06-28 15:59 ` Jeff Moyer
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=x497crnefwj.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=evn@google.com \
--cc=gpiccoli@igalia.com \
--cc=io-uring@vger.kernel.org \
--cc=jordyzomer@google.com \
--cc=keescook@chromium.org \
--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 \
--cc=steve@sk2.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®