From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: qgroup: Don't trigger backref walk at delayed ref insert time (Re: Kernel traces)
Date: Fri, 26 Jul 2019 18:31:32 +0200 [thread overview]
Message-ID: <20190726163132.GA29895@cuci.nl> (raw)
In-Reply-To: <9b81647b-66c2-9870-161f-084b7d41af9c@gmx.com>
Qu Wenruo wrote:
>It's caused by qgroup, and a dead lock on btrfs_drop_snapshot().
>This is one of the easiest way to trigger an ABBA deadlock.
>Please either disable qgroup or apply this patch to solve it:
>https://patchwork.kernel.org/patch/10725371/
Can anyone confirm that patch https://patchwork.kernel.org/patch/10725371/
(qgroup: Don't trigger backref walk at delayed ref insert time)
is present in mainline Linux kernel v5.2.2 ?
I seem to be getting a conflict on merging that patch with this kernel.
--
Stephen.
next prev parent reply other threads:[~2019-07-26 16:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 12:05 Kernel traces Stephen R. van den Berg
2018-12-10 16:54 ` Chris Murphy
2018-12-11 11:52 ` Stephen R. van den Berg
2018-12-12 6:16 ` Chris Murphy
2018-12-12 7:26 ` Stephen R. van den Berg
2018-12-12 21:01 ` Chris Murphy
2018-12-28 9:20 ` Stephen R. van den Berg
2018-12-28 10:10 ` Qu Wenruo
2018-12-28 13:40 ` Stephen R. van den Berg
2018-12-28 13:46 ` Qu Wenruo
2018-12-28 15:00 ` Stephen R. van den Berg
2019-01-23 15:50 ` Stephen R. van den Berg
2019-01-25 8:01 ` New hang (Re: Kernel traces), sysreq+w output Stephen R. van den Berg
2019-01-25 8:04 ` Stephen R. van den Berg
2019-02-05 22:18 ` Stephen R. van den Berg
2019-02-06 0:22 ` Qu Wenruo
2019-02-06 0:36 ` Martin Raiber
2019-07-26 16:31 ` Stephen R. van den Berg [this message]
2019-07-26 23:24 ` qgroup: Don't trigger backref walk at delayed ref insert time (Re: Kernel traces) Qu Wenruo
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=20190726163132.GA29895@cuci.nl \
--to=srb@cuci.nl \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).