linux-kernel - Re: [tip:locking/core 24/43] mm/huge_memory.c:4055:8: warning: spinlock 'xas.xa->xa_lock' is not held on every path through here

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] [day] [month] [year] [list]

Message-ID: <20260121151857.GF166857@noisy.programming.kicks-ass.net>
Date: Wed, 21 Jan 2026 16:18:57 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Philip Li <philip.li@...el.com>
Cc: kernel test robot <lkp@...el.com>, Marco Elver <elver@...gle.com>,
	llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
	linux-kernel@...r.kernel.org, x86@...nel.org,
	Bart Van Assche <bvanassche@....org>
Subject: Re: [tip:locking/core 24/43] mm/huge_memory.c:4055:8: warning:
 spinlock 'xas.xa->xa_lock' is not held on every path through here

On Wed, Jan 21, 2026 at 11:17:22PM +0800, Philip Li wrote:
> On Wed, Jan 21, 2026 at 03:31:00PM +0100, Peter Zijlstra wrote:
> > On Wed, Jan 21, 2026 at 10:27:16PM +0800, kernel test robot wrote:
> > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
> > > head:   ccf9e070116a81d29aae30db501d562c8efd1ed8
> > > commit: 6e530e2e31191d88f692e6c8d3bd245e43416e4f [24/43] debugfs: Make debugfs_cancellation a context lock struct
> > > config: s390-randconfig-002-20260121 (https://download.01.org/0day-ci/archive/20260121/202601212251.RuHvsKd5-lkp@intel.com/config)
> > 
> > Again, that is:
> > 
> >  CONFIG_WARN_CONTEXT_ANALYSIS_ALL=y
> > 
> > Robot folks, could you filter out those configs from the randconfig set?
> > At this time, it has no value reporting these.
> 
> Sorry for the meaningless report, i will update the bot to disable this config.

No problem. Thanks for removing it!