linux-kernel - Re: [PATCH v2 1/1] Add a new sysctl to disable io

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 29 Jun 2023 14:36:37 -0400
From:   Gabriel Krisman Bertazi <krisman@...e.de>
To:     Matteo Rizzo <matteorizzo@...gle.com>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        io-uring@...r.kernel.org, jordyzomer@...gle.com, evn@...gle.com,
        poprdi@...gle.com, corbet@....net, axboe@...nel.dk,
        asml.silence@...il.com, akpm@...ux-foundation.org,
        keescook@...omium.org, rostedt@...dmis.org,
        dave.hansen@...ux.intel.com, ribalda@...omium.org,
        chenhuacai@...nel.org, steve@....org, gpiccoli@...lia.com,
        ldufour@...ux.ibm.com, bhe@...hat.com, oleksandr@...alenko.name
Subject: Re: [PATCH v2 1/1] Add a new sysctl to disable io_uring system-wide

Matteo Rizzo <matteorizzo@...gle.com> writes:

> 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, all calls to
> io_uring_setup fail with -EPERM unless the calling process has
> CAP_SYS_ADMIN. When 2, calls to io_uring_setup fail with -EPERM
> regardless of privilege.
>
> Signed-off-by: Matteo Rizzo <matteorizzo@...gle.com>
> ---

Thanks for adding the extra level for root-only rings.

The patch looks good to me.

Reviewed-by: Gabriel Krisman Bertazi <krisman@...e.de>

-- 
Gabriel Krisman Bertazi