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]
Message-ID: <CAG48ez3k2K1_gwxo=ckHQmHxXgV-VfQ897-TXQcJjUcdiyr4Hg@mail.gmail.com>
Date:   Fri, 30 Jun 2023 17:15:44 +0200
From:   Jann Horn <jannh@...gle.com>
To:     Matteo Rizzo <matteorizzo@...gle.com>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        io-uring@...r.kernel.org, axboe@...nel.dk, asml.silence@...il.com,
        corbet@....net, akpm@...ux-foundation.org, keescook@...omium.org,
        ribalda@...omium.org, rostedt@...dmis.org, chenhuacai@...nel.org,
        gpiccoli@...lia.com, ldufour@...ux.ibm.com, evn@...gle.com,
        poprdi@...gle.com, jordyzomer@...gle.com, jmoyer@...hat.com,
        krisman@...e.de
Subject: Re: [PATCH v3 1/1] io_uring: add a sysctl to disable io_uring system-wide

On Fri, Jun 30, 2023 at 5:10 PM Matteo Rizzo <matteorizzo@...gle.com> 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, 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>
> Reviewed-by: Jeff Moyer <jmoyer@...hat.com>
> Reviewed-by: Gabriel Krisman Bertazi <krisman@...e.de>

Reviewed-by: Jann Horn <jannh@...gle.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ