linux-kernel - Re: [PATCH v6 2/3] io_uring: add IOURING_REGISTER

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] [day] [month] [year] [list]

Message-ID: <20210107083932.ho6vo5g5hmdohwqt@steredhat>
Date:   Thu, 7 Jan 2021 09:39:32 +0100
From:   Stefano Garzarella <sgarzare@...hat.com>
To:     Daurnimator <quae@...rnimator.com>
Cc:     Jens Axboe <axboe@...nel.dk>,
        Kernel Hardening <kernel-hardening@...ts.openwall.com>,
        Christian Brauner <christian.brauner@...ntu.com>,
        io-uring <io-uring@...r.kernel.org>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Stefan Hajnoczi <stefanha@...hat.com>,
        Jann Horn <jannh@...gle.com>, Jeff Moyer <jmoyer@...hat.com>,
        Aleksa Sarai <asarai@...e.de>,
        Sargun Dhillon <sargun@...gun.me>,
        linux-kernel@...r.kernel.org, Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH v6 2/3] io_uring: add IOURING_REGISTER_RESTRICTIONS opcode

On Mon, Jan 04, 2021 at 01:26:41AM +1100, Daurnimator wrote:
>On Fri, 28 Aug 2020 at 00:59, Stefano Garzarella <sgarzare@...hat.com> wrote:
>> +               __u8 register_op; /* IORING_RESTRICTION_REGISTER_OP */
>
>Can you confirm that this intentionally limited the future range of
>IORING_REGISTER opcodes to 0-255?
>

It was based on io_uring_probe, so we used u8 for opcodes, but we have 
room to extend it in the future.

So, for now, this allow to register restrictions up to 255 
IORING_REGISTER opcode.