From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: l@damenly.su, linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: Re: [PATCH V5 1/2] btrfs: fix lockdep warning while mounting sprout fs
Date: Fri, 3 Sep 2021 07:51:10 +0800 [thread overview]
Message-ID: <c71323a0-edb2-3994-babf-4ff8c3fac1e8@oracle.com> (raw)
In-Reply-To: <5c9c7e1e-7909-f9a7-6e4d-9265e1bd0d5b@suse.com>
On 31/08/2021 16:18, Nikolay Borisov wrote:
>
>
> On 31.08.21 г. 4:21, Anand Jain wrote:
>> Following test case reproduces lockdep warning.
>>
>> Test case:
>>
>> $ mkfs.btrfs -f <dev1>
>> $ btrfstune -S 1 <dev1>
>> $ mount <dev1> <mnt>
>> $ btrfs device add <dev2> <mnt> -f
>> $ umount <mnt>
>> $ mount <dev2> <mnt>
>> $ umount <mnt>
>>
>> The warning claims a possible ABBA deadlock between the threads initiated by
>> [#1] btrfs device add and [#0] the mount.
>>
>
> Send this as an xfstest
The above steps are the most common in the seed group of test cases.
The first test case (btrfs/161) in the -g seed group already reproduces
the lock dep warning.
Any idea how do I reset the lockdep warning (without reboot) so that it
will again report the same lockdep warning stack if it discovers again?
Thanks, Anand
>
> <snip>
>
next prev parent reply other threads:[~2021-09-02 23:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 1:21 [PATCH V5 0/2] btrfs: device_list_mutex fix lockdep warn and cleanup Anand Jain
2021-08-31 1:21 ` [PATCH V5 1/2] btrfs: fix lockdep warning while mounting sprout fs Anand Jain
2021-08-31 8:18 ` Nikolay Borisov
2021-09-02 23:51 ` Anand Jain [this message]
2021-08-31 12:37 ` Nikolay Borisov
2021-09-01 0:49 ` Su Yue
2021-09-02 15:28 ` David Sterba
2021-08-31 1:21 ` [PATCH RFC V5 2/2] btrfs: consolidate device_list_mutex in prepare_sprout to its parent Anand Jain
2021-08-31 13:03 ` Nikolay Borisov
2021-09-03 3:08 ` Anand Jain
2021-09-17 15:37 ` David Sterba
2021-09-18 0:10 ` Anand Jain
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=c71323a0-edb2-3994-babf-4ff8c3fac1e8@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=l@damenly.su \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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).