From: Bart Van Assche <bvanassche@acm.org>
To: Matteo Rizzo <matteorizzo@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
io-uring@vger.kernel.org
Cc: 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,
ribalda@chromium.org, 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: Tue, 27 Jun 2023 10:10:36 -0700 [thread overview]
Message-ID: <e8924389-985a-42ad-9daf-eca2bf12fa57@acm.org> (raw)
In-Reply-To: <20230627120058.2214509-2-matteorizzo@google.com>
On 6/27/23 05:00, Matteo Rizzo wrote:
> +Prevents all processes from creating new io_uring instances. Enabling this
> +shrinks the kernel's attack surface.
> +
> += =============================================================
> +0 All processes can create io_uring instances as normal. This is the default
> + setting.
> +1 io_uring is disabled. io_uring_setup always fails with -EPERM. Existing
> + io_uring instances can still be used.
> += =============================================================
I'm using fio + io_uring all the time on Android devices. I think we need a
better solution than disabling io_uring system-wide, e.g. a mechanism based
on SELinux that disables io_uring for apps and that keeps io_uring enabled
for processes started via 'adb root && adb shell ...'
Bart.
next prev parent reply other threads:[~2023-06-27 17:10 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 [this message]
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
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=e8924389-985a-42ad-9daf-eca2bf12fa57@acm.org \
--to=bvanassche@acm.org \
--cc=akpm@linux-foundation.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--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®