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] [day] [month] [year] [list]
Message-ID: <biqcjscrlgfmznvysigpkqqyr3xvy7dbtmdwwxf4bkirbri5l5@rgkuif4novc6>
Date: Fri, 18 Jul 2025 10:45:47 +0200
From: Carlos Maiolino <cem@...nel.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, 
	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 01:33:18AM -0700, Christoph Hellwig wrote:
> On Fri, Jul 18, 2025 at 10:30:56AM +0200, Carlos Maiolino wrote:
> > 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?
> 
> You'll need CONFIG_MEMORY_FAILURE and CONFIG_FS_DAX to trigger this.
> All my test setups seem to lack the former.
> 

Heh, same. I'll default my build tests to use allmodconfig.

Thanks hch.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ