linux-kernel - Re: linux-next: build failure after merge of the xfs 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 for Android: free password hash cracker in your pocket

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

Message-ID: <hmc6flnzhy3fvryk5c4bjgo7qehhnfpecm2w6wfyz7q7wly3a4@nvo6ow5j3ffl>
Date: Fri, 18 Jul 2025 10:30:56 +0200
From: Carlos Maiolino <cem@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: David Chinner <david@...morbit.com>, linux-xfs@...r.kernel.org, 
	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 xfs tree

On Fri, Jul 18, 2025 at 10:08:36AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the xfs tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> fs/xfs/xfs_notify_failure.c: In function 'xfs_dax_notify_dev_failure':
> fs/xfs/xfs_notify_failure.c:353:1: error: label 'out' defined but not used [-Werror=unused-label]
>   353 | out:
>       | ^~~
> 
> Caused by commit
> 
>   e967dc40d501 ("xfs: return the allocated transaction from xfs_trans_alloc_empty")
> 
> I have used the xfs tree from next-20250717 for today.

Thanks for the heads up Stephen. I didn't catch those errors while build
testing here. Could you please share with me the build options you usually
use so I can tweak my system to catch those errors before pushing them to
linux-next?

Carlos

> 
> -- 
> Cheers,
> Stephen Rothwell