From: Su Yue <l@damenly.su>
To: dsterba@suse.cz
Cc: Anand Jain <anand.jain@oracle.com>,
dsterba@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V5 0/4] btrf_show_devname related fixes
Date: Wed, 01 Sep 2021 07:55:49 +0800 [thread overview]
Message-ID: <wno1p3rx.fsf@damenly.su> (raw)
In-Reply-To: <20210831154104.GL3379@suse.cz>
On Tue 31 Aug 2021 at 17:41, David Sterba <dsterba@suse.cz> wrote:
> On Tue, Aug 31, 2021 at 10:28:24PM +0800, Su Yue wrote:
>>
>> On Tue 31 Aug 2021 at 06:41, Anand Jain <anand.jain@oracle.com>
>> wrote:
>>
>> > Ping.
>> >
>> In the past week, I spent some time on testing this patchset
>> and
>> the patch 'btrfs: fix lockdep warning while mounting sprout
>> fs'.
>>
>> Same as you, I wonder if there is any race condition. Just
>> wrote
>> some scripts including device removal, replace and sprout while
>> busy looping showing mount info. It runned well and passed
>> xfstests
>> in my two VMs. I'm not a pundit in btrfs device field so I
>> can't
>> give my
>> RBs even these patches looks almost okay to me.
>
> So this could be a Tested-by if you want.
Sure. Thanks.
--
Su
next prev parent reply other threads:[~2021-08-31 23:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 5:05 [PATCH V5 0/4] btrf_show_devname related fixes Anand Jain
2021-08-24 5:05 ` [PATCH V5 1/4] btrfs: convert latest_bdev type to struct btrfs_device and rename Anand Jain
2021-08-24 5:05 ` [PATCH RFC V5 2/4] btrfs: use latest_dev in btrfs_show_devname Anand Jain
2021-09-02 13:47 ` David Sterba
2021-08-24 5:05 ` [PATCH V5 3/4] btrfs: update latest_dev when we sprout Anand Jain
2021-08-24 5:05 ` [PATCH V5 4/4] btrfs: fix comment about the btrfs_show_devname Anand Jain
2021-09-02 14:26 ` David Sterba
2021-09-02 14:38 ` David Sterba
2021-08-30 22:41 ` [PATCH V5 0/4] btrf_show_devname related fixes Anand Jain
2021-08-31 14:28 ` Su Yue
2021-08-31 15:41 ` David Sterba
2021-08-31 23:55 ` Su Yue [this message]
2021-08-31 23:58 ` Su Yue
2021-09-02 15:26 ` David Sterba
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=wno1p3rx.fsf@damenly.su \
--to=l@damenly.su \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.