From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Chandan Babu R <chandanbabu@kernel.org>,
Linux-XFS mailing list <linux-xfs@vger.kernel.org>
Subject: Re: [BUG REPORT] Deadlock when executing xfs/708 on xfs-linux's for-next
Date: Wed, 8 May 2024 21:56:07 -0700 [thread overview]
Message-ID: <ZjxXZ6i_4_5BYVVK@infradead.org> (raw)
In-Reply-To: <20240508160933.GA360919@frogsfrogsfrogs>
On Wed, May 08, 2024 at 09:09:33AM -0700, Darrick J. Wong wrote:
> > Do you have any odd kasan/lockdep features enabled?
>
> Never mind that.
>
> I /think/ I figured this out -- the xfarray_sort_scan function can
> return an error if a fatal signal has been received. Unfortunately the
> callsites all assume that an error return means that si->folio doesn't
> point at a folio, so they don't bother calling xfarray_sort_scan_done,
> so we leak a locked page and that's what the folio_wait_bit_common is
> stuck on.
Yes, this looks a lot like it is tripping over a locked page.
prev parent reply other threads:[~2024-05-09 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 4:17 [BUG REPORT] Deadlock when executing xfs/708 on xfs-linux's for-next Chandan Babu R
2024-05-07 22:20 ` Darrick J. Wong
2024-05-08 16:09 ` Darrick J. Wong
2024-05-09 4:56 ` Christoph Hellwig [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=ZjxXZ6i_4_5BYVVK@infradead.org \
--to=hch@infradead.org \
--cc=chandanbabu@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).