linux-kernel - Re: deconflicting new syscall numbers for 6.11

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: <CAHk-=whabFzoT+iLSF1A-u-4fBvtLGMBvi67xUOqww7PGp2B8Q@mail.gmail.com>
Date: Thu, 4 Jul 2024 15:07:31 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: "Jason A . Donenfeld" <Jason@...c4.com>, Jiri Olsa <jolsa@...nel.org>, 
	Masami Hiramatsu <mhiramat@...nel.org>, cgzones@...glemail.com, 
	Christian Brauner <brauner@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: deconflicting new syscall numbers for 6.11

On Thu, 4 Jul 2024 at 14:45, Arnd Bergmann <arnd@...db.de> wrote:
>
> It's not random, it's all the architectures: the ones that
> don't have a syscall.tbl file are the ones that use the table
> in include/uapi/asm-generic/unistd.h.

Ok.

I think it's bogus to reseve system calls for everybody even when it
makes no sense.

But it's also pretty moot, since I think the whole system call has to go away.

All it is is an odd wrapper around mmap() anyway, and it's a useful
enough thing *outside* of getrandom() that I pretty much guarantee it
will be used for other things than vgetrandom anyway.

              Linus