From: Christoph Hellwig <hch@infradead.org>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@vger.kernel.org
Subject: Re: Deadlock between block allocation and block truncation
Date: Tue, 25 Apr 2017 00:36:08 -0700 [thread overview]
Message-ID: <20170425073608.GA7311@infradead.org> (raw)
In-Reply-To: <20170414074244.GA18519@infradead.org>
FYI, I've been testing with the patch quite a bit and it seems to
be doing fine.
But I fear it's not the complete fix: if we do truncates, hole
punches or other complicated operations the bmap btree blocks
might be from different AGs than the data blocks and we could
still run into these issues in theory. So I fear we might have
to come up with a solution where we roll into a new chained transaction
everytime we encounter a new AG instead.
prev parent reply other threads:[~2017-04-25 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 15:51 Deadlock between block allocation and block truncation Nikolay Borisov
2017-04-12 16:10 ` Christoph Hellwig
2017-04-12 16:12 ` Nikolay Borisov
2017-04-12 16:20 ` Christoph Hellwig
2017-04-12 17:44 ` Nikolay Borisov
2017-04-12 17:57 ` Christoph Hellwig
2017-04-13 13:52 ` Nikolay Borisov
2017-04-14 7:42 ` Christoph Hellwig
2017-04-25 7:36 ` 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=20170425073608.GA7311@infradead.org \
--to=hch@infradead.org \
--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