[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250619-rennpferd-annexion-f24c89ba6088@brauner>
Date: Thu, 19 Jun 2025 10:43:53 +0200
From: Christian Brauner <brauner@...nel.org>
To: kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com,
Christian Brauner <christianvanbrauner@...il.com>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [brauner-vfs:work.pidfs.xattr] [pidfs] e3bfecb731:
WARNING:possible_irq_lock_inversion_dependency_detected
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.
Powered by blists - more mailing lists