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-=wjM4kDjVSMwJoasuJDFfzh+sZDxO0qxMCPLZ0G1xNoKqA@mail.gmail.com>
Date: Fri, 5 Jul 2024 09:59:08 -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 Fri, 5 Jul 2024 at 01:34, Arnd Bergmann <arnd@...db.de> wrote:
>
> I see. Just to make sure: do you think it's ok to still
> reserve system call numbers everywhere if they are used
> on most architectures?

Yes. If there's a reason why a system call might be used, no problem.

             Linus