linux-kernel - Re: [PATCH 0/2] clone3 fixes

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: <CAK8P3a23y0UFbu-po-Umh-=9DUTpRyzRkB=RxJd1A+YJVTTGrA@mail.gmail.com>
Date:   Sun, 14 Jul 2019 22:07:13 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Christian Brauner <christian@...uner.io>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] clone3 fixes

On Sun, Jul 14, 2019 at 9:22 PM Christian Brauner <christian@...uner.io> wrote:
>
> Hey everyone,
>
> Here are two small fixes/improvements for the clone3 syscall that I plan
> on sending soon.
>
> The first patches reserves the clone3 syscalls number 435 across all
> architectures by placing a commit in the corresponding syscall tables of
> architectures that do not yet implement clone3. This is done to preserve
> the identical numbering for all new syscalls that Arnd introduced.
>
> The second patch dates back to a discussion with Arnd when I suggested
> reserving the syscall number. Arnd suggested to ensure that we catch all
> arches that do implement clone3 without explicitly setting
> __ARCH_WANT_SYS_CLONE3.

Both patches

Reviewed-by: Arnd Bergmann <arnd@...db.de>