linux-kernel - Re: linux-next: manual merge of the random tree with the vfs-brauner, ftrace trees

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 2 Jul 2024 16:43:17 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "Theodore Ts'o" <tytso@....edu>, Christian Brauner <brauner@...nel.org>, 
	Steven Rostedt <rostedt@...dmis.org>, Masami Hiramatsu <mhiramat@...nel.org>, 
	Christian Göttsche <cgzones@...glemail.com>, 
	Jiri Olsa <jolsa@...nel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the random tree with the vfs-brauner,
 ftrace trees

Hi Stephen,

On Tue, Jul 2, 2024 at 8:56 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>  +466   n32     removexattrat                   sys_removexattrat
> ++468   n32     vgetrandom_alloc                sys_vgetrandom_alloc

Wondering why 467 was skipped.

Also, any chance you can let me keep 463 and shift the others (unless
Christian objects)? Or does it not really matter anyway because Linus
is gonna merge this how he wants, separately from what you do in
-next?

Jason