From: Dave Chinner <dgc@kernel.org>
To: Ammar Faizi <ammarfaizi2@openresty.com>
Cc: Linux XFS Mailing List <linux-xfs@vger.kernel.org>,
Linux FSdevel Mailing List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yichun Zhang <yichun@openresty.com>,
Junlong Li <lijunlong@openresty.com>,
Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
gwml@gnuweeb.org
Subject: Re: XFS Deadlock on Linux 6.12.82
Date: Thu, 23 Apr 2026 06:52:10 +1000 [thread overview]
Message-ID: <aek0-rq8zX-ta6aW@dread> (raw)
In-Reply-To: <20260422152505.818254-1-ammarfaizi2@openresty.com>
On Wed, Apr 22, 2026 at 10:25:05PM +0700, Ammar Faizi wrote:
> Hi,
>
> While running Linux 6.12.82 with CONFIG_PROVE_LOCKING enabled, I
> encountered the following lockdep splat. Based on the call trace, the
> potential deadlock appears to be related to the XFS subsystem.
Well known false positive.
Lockdep knows nothing about inode reference counts and how they
interact with memory reclaim. i.e. A referenced locked inode doing
memory allocation cannot be found by memory reclaim processing
unreferenced inodes, so reclaim cannot deadlock on inode locks held
by referenced inodes when doing memory allocation.
-Dave.
--
Dave Chinner
dgc@kernel.org
prev parent reply other threads:[~2026-04-22 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 15:25 XFS Deadlock on Linux 6.12.82 Ammar Faizi
2026-04-22 20:52 ` Dave Chinner [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=aek0-rq8zX-ta6aW@dread \
--to=dgc@kernel.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@openresty.com \
--cc=gwml@gnuweeb.org \
--cc=lijunlong@openresty.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yichun@openresty.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