[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260121143100.GC166857@noisy.programming.kicks-ass.net>
Date: Wed, 21 Jan 2026 15:31:00 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: kernel test robot <lkp@...el.com>
Cc: 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 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.
Powered by blists - more mailing lists