public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Nikolay Borisov <n.borisov.lkml@gmail.com>,
	Christoph Hellwig <hch@lst.de>,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH, RFC] xfs: fix multi-AG deadlock in xfs_bunmapi
Date: Wed, 19 Jul 2017 09:36:43 +0200	[thread overview]
Message-ID: <20170719073643.GA21259@lst.de> (raw)
In-Reply-To: <20170718183351.GK4224@magnolia>

On Tue, Jul 18, 2017 at 11:33:51AM -0700, Darrick J. Wong wrote:
> On Tue, Jul 18, 2017 at 09:27:43PM +0300, Nikolay Borisov wrote:
> > 
> > 
> > On 18.07.2017 21:15, Darrick J. Wong wrote:
> > > On Tue, Jul 18, 2017 at 07:25:45PM +0200, Christoph Hellwig wrote:
> > >> Just like in the allocator we must avoid touching multiple AGs out of
> > >> order when freeing blocks, as freeing still locks the AGF and can cause
> > >> the same AB-BA deadlocks as in the allocation path.
> > >>
> > >> Signed-off-by: Christoph Hellwig <hch@lst.de>
> > >> Reported-by: Nikolay Borisov <n.borisov.lkml@gmail.com>
> > > 
> > > Looks ok, though I wonder what the bug report looked like. :)
> > 
> > https://www.spinics.net/lists/linux-xfs/msg05918.html
> 
> Ah, ok.  That's what I suspected, so I'm glad to have confirmation.

Btw, I found a little bug when rebasing additional bunmapi work on
top of the patch - we need to add a !isrt to the conditional for
the AG check.  But I'll wait for test results from Nikolay before
resending it, as it should not affect normal non-RT setups.

  reply	other threads:[~2017-07-19  7:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 17:25 [PATCH, RFC] xfs: fix multi-AG deadlock in xfs_bunmapi Christoph Hellwig
2017-07-18 18:15 ` Darrick J. Wong
2017-07-18 18:27   ` Nikolay Borisov
2017-07-18 18:33     ` Darrick J. Wong
2017-07-19  7:36       ` Christoph Hellwig [this message]
2017-07-19 13:11 ` Nikolay Borisov
2017-07-19 15:09   ` Nikolay Borisov
2017-07-20  7:47     ` Christoph Hellwig
2017-07-20  7:47       ` Nikolay Borisov
2017-07-20  7:49         ` Christoph Hellwig
2017-07-20  7:51           ` Nikolay Borisov
2017-07-20 14:58           ` Nikolay Borisov
2017-07-21 10:26             ` Christoph Hellwig
2017-07-26 13:04             ` Christoph Hellwig
2017-07-26 13:59               ` Nikolay Borisov
2017-07-28  6:05               ` Nikolay Borisov
2017-07-31 12:09                 ` Christoph Hellwig

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=20170719073643.GA21259@lst.de \
    --to=hch@lst.de \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=n.borisov.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