mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Christian Brauner <christianvanbrauner@gmail.com>,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<oliver.sang@intel.com>
Subject: Re: [brauner-vfs:work.pidfs.xattr] [pidfs]  e3bfecb731: WARNING:possible_irq_lock_inversion_dependency_detected
Date: Fri, 20 Jun 2025 10:00:56 +0800	[thread overview]
Message-ID: <aFTA2F1ubYQX4sLA@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20250619-rennpferd-annexion-f24c89ba6088@brauner>

hi, Christian Brauner,

On Thu, Jun 19, 2025 at 10:43:53AM +0200, Christian Brauner wrote:
> On Thu, Jun 19, 2025 at 03:27:28PM +0800, kernel test robot wrote:
> > 
> > 
> > Hello,
> > 
> > kernel test robot noticed "WARNING:possible_irq_lock_inversion_dependency_detected" on:
> > 
> > commit: e3bfecb7310ade68457392f0e7d4c4ec22d0a401 ("pidfs: keep pidfs dentry stashed once created")
> > https://git.kernel.org/cgit/linux/kernel/git/vfs/vfs.git work.pidfs.xattr
> > 
> > in testcase: boot
> > 
> > config: x86_64-randconfig-078-20250618
> > compiler: gcc-12
> > test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
> > 
> > (please refer to attached dmesg/kmsg for entire log/backtrace)
> 
> The branch is irrelevant. I can delete it so it doesn't trigger kbuild.

thanks a lot for information!

      reply	other threads:[~2025-06-20  2:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  7:27 kernel test robot
2025-06-19  8:43 ` Christian Brauner
2025-06-20  2:00   ` Oliver Sang [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=aFTA2F1ubYQX4sLA@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=brauner@kernel.org \
    --cc=christianvanbrauner@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    /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
all inboxes | Powered by JetHome®