From: Dave Chinner <david@fromorbit.com>
To: 张本龙 <zbl.lkml@gmail.com>
Cc: linux-xfs@vger.kernel.org, Brian Foster <bfoster@redhat.com>
Subject: Re: XFS: 3-way deadlock with xfs_dquot, xfs_buf and xfs_inode
Date: Tue, 18 Dec 2018 15:36:26 +1100 [thread overview]
Message-ID: <20181218043626.GA31274@dastard> (raw)
In-Reply-To: <CAJDdQW2U5hE2W245iodcOF408DV8W1D1-MSRtSMvY8=TT9rnCg@mail.gmail.com>
On Tue, Dec 18, 2018 at 10:41:48AM +0800, 张本龙 wrote:
> Dave Chinner <david@fromorbit.com> 于2018年12月18日周二 上午7:33写道:
> >
> > On Sat, Dec 15, 2018 at 01:34:33PM +0800, 张本龙 wrote:
> > > Hi Developpers and XFS,
> > >
> > > There seems to be a deadlock involving 3 threads: 1) the fsync thread
> > > has acquired the project quota lock, and is trying to get the xfs_buf
> > > (it's a an agf); 2) the xfs_buf is attached to a transaction, and
> > > xfs_end_io is trying to get the xfs_inode ilock; 3) the write thread
> > > has acquired the xfs_inode ilock, and tries to get the xfs_dquot.
> > > Below are the traces.
> >
> > I don't see a deadlock here. What's holding the AGF lock and
> > preventing progress from being made?
> >
>
> Oh, I was thinking the AGF is attached to a transaction.
it may be, but it has to be locked to be joined to a transaction.
> So between
> xfs_trans_bjoin() and xfs_trans_commit(), a buf cannot be used by
> others right? Then it should be released by xfs_end_io() in
> xfs_trans_commit(),
No, because that transaction doesn't hold the AGF.
> and the deadlock is like:
>
> Thread 1 2
> 3
> fsync()
> dqlock P
> agf lock
> <blocks>
> xfs_end_io
> (agf locked by transaction)
> ilock A
> <blocks>
> unlock agf in trans commit
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is wrong.
There is no AGF held in the ioend transaction in progress.
xfs_setfilesize() only needs to lock the inode as that is all it
modifies. It's also compeltely independent of the transaction being
run in the fsync context unless they have ot modify the same
metadata (which they don't).
Use 'echo w > /proc/sysrq-trigger' to list all the blocked
processes. Maybe one of them is holding the AGF locked and is
waiting on something else...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2018-12-18 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 5:34 XFS: 3-way deadlock with xfs_dquot, xfs_buf and xfs_inode 张本龙
2018-12-17 23:33 ` Dave Chinner
2018-12-18 2:41 ` 张本龙
2018-12-18 4:36 ` 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=20181218043626.GA31274@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zbl.lkml@gmail.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