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:
 <FR2P281MB1544E97499E8EA3C06C4D0C4B515A@FR2P281MB1544.DEUP281.PROD.OUTLOOK.COM>
Date: Mon, 15 Sep 2025 06:35:43 +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

Hi all,

On Wed, 2025-09-10 at 02:50 +0200, Stephen Rothwell wrote:
> > I am still seeing this failure.

Sorry to have caused such trouble. A patch fixing this failure was
submitted to LKML as soon as LKP reported the failures, but I believe that
one may have been lost during the pickup process:

https://lore.kernel.org/lkml/20250904-trace-task-newtask-fix-callbacks-v1-1-8edb3d557365@siemens-energy.com/

> From today, I have instead just reverted these three commits:
>
>   c6ac444ff20c ("nios2: implement architecture-specific portion of sys_clone3")
>   bbc46b23af5b ("arch: copy_thread: pass clone_flags as u64")
>   edd3cb05c00a ("copy_process: pass clone_flags as u64 across calltree")

Thank you, sounds sensible to me; especially since this leaves the
actual bugfix commit of the series ('Fixes: b612e5df4587 ("clone3: add
CLONE_CLEAR_SIGHAND")') in tree.
However, I still see value in having the other changes make their way
into mainline, eventually, as they address a build-time warning on nios2
and improve portability to 32bit architectures. What is the best course
of action here? Reroll them into a v3, along with the patch above, or
wait for an eventual pickup of the patch on its own?

Best regards,
Simon