From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [viro-vfs:work.dcache2] [__dentry_kill()] 01b17d53ce: WARNING:possible_recursive_locking_detected
Date: Mon, 13 Nov 2023 08:06:50 +0000 [thread overview]
Message-ID: <20231113080650.GQ1957730@ZenIV> (raw)
In-Reply-To: <202311131520.ff2c101e-oliver.sang@intel.com>
On Mon, Nov 13, 2023 at 03:59:04PM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed "WARNING:possible_recursive_locking_detected" on:
>
> commit: 01b17d53ce197777be701269395edba2fe27069a ("__dentry_kill(): new locking scheme")
> https://git.kernel.org/cgit/linux/kernel/git/viro/vfs.git work.dcache2
*shrug*
False positive, and yes, it needs the spin_lock_nested() when taking
->d_lock on victim after having just acquired it on the parent.
prev parent reply other threads:[~2023-11-13 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 7:59 [viro-vfs:work.dcache2] [__dentry_kill()] 01b17d53ce: WARNING:possible_recursive_locking_detected kernel test robot
2023-11-13 8:06 ` Al Viro [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=20231113080650.GQ1957730@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).