From: Peter Zijlstra <peterz@infradead.org>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>, Marco Elver <elver@google.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
Bart Van Assche <bvanassche@acm.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
Date: Wed, 21 Jan 2026 16:18:57 +0100 [thread overview]
Message-ID: <20260121151857.GF166857@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <aXDuAoDeFOhHvHAP@rli9-mobl>
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!
prev parent reply other threads:[~2026-01-21 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 14:27 [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 kernel test robot
2026-01-21 14:31 ` Peter Zijlstra
2026-01-21 15:17 ` Philip Li
2026-01-21 15:18 ` Peter Zijlstra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260121151857.GF166857@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bvanassche@acm.org \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=philip.li@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox