linux-kernel - Re: linux-next: build failure after merge of the vfs-brauner tree

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:
 <FR2P281MB154466417264801491E8001EB500A@FR2P281MB1544.DEUP281.PROD.OUTLOOK.COM>
Date: Thu, 4 Sep 2025 07:44:19 +0000
From: "schuster.simon@...mens-energy.com" <schuster.simon@...mens-energy.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Christian Brauner
	<brauner@...nel.org>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the vfs-brauner tree

On Thu, Sept 4, 2025 at 03:34:00AM +0200, Stephen Rothwell wrote:
> After merging the vfs-brauner tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ...
>
> Presumably caused by commit
>
>   edd3cb05c00a ("copy_process: pass clone_flags as u64 across calltree")
>
> I have used the vfs-brauner tree from next-20250829 for today.

Thanks for investigating and notifying me. Yes, bisect is almost
certainly correct. It looks like I missed adapting the tracepoint
consumers of the task_newtask tracepoint that I did adapt in that
commit, sorry. I'll look into preparing a patch for it.

Best regards
Simon