From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com, l@damenly.su
Subject: Re: [PATCH v4 0/4] btrf_show_devname related fixes
Date: Mon, 23 Aug 2021 21:46:18 +0200 [thread overview]
Message-ID: <20210823194618.GT5047@twin.jikos.cz> (raw)
In-Reply-To: <cover.1629458519.git.anand.jain@oracle.com>
On Mon, Aug 23, 2021 at 07:31:38PM +0800, Anand Jain wrote:
> These fixes are inspired by the bug report and its discussions in the
> mailing list subject
> btrfs: traverse seed devices if fs_devices::devices is empty in show_devname
>
> And depends on the patch
> [PATCH v2] btrfs: fix lockdep warning while mounting sprout fs
> in the ML
>
> v4:
> Fix unrelated changes in 2/4
> v3:
> Fix rcu_lock in the patch 3/4
>
> Anand Jain (4):
> btrfs: consolidate device_list_mutex in prepare_sprout to its parent
> btrfs: save latest btrfs_device instead of its block_device in
> fs_devices
> btrfs: use latest_dev in btrfs_show_devname
> btrfs: update latest_dev when we sprout
Patchset survived one round of fstests and I haven't seen the lockdep
warning in btrfs/020 that's caused by some unrelated work in loop device
driver. There's a series from Josef to fix it by shuffling locking, so
it would be interesting to see where's the difference.
next prev parent reply other threads:[~2021-08-23 19:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210823113138.jOljK3KLS8c1v1kFdbAV_tpEHFy5LjD3UB6FOO8_EtI@z>
2021-08-23 11:31 ` [PATCH v4 0/4] btrf_show_devname related fixes Anand Jain
2021-08-20 11:28 ` [PATCH v3 2/4] btrfs: save latest btrfs_device instead of its block_device in fs_devices Anand Jain
2021-08-21 14:46 ` Su Yue
2021-08-23 3:03 ` Anand Jain
2021-08-20 11:32 ` [PATCH v3 0/4] btrf_show_devname related fixes Anand Jain
[not found] ` <20210823113139.43q6FCDq3tjx-V8qI6siPYNNaZMOHzbIqHie5SvqOMw@z>
2021-08-23 11:31 ` [PATCH RFC v4 1/4] btrfs: consolidate device_list_mutex in prepare_sprout to its parent Anand Jain
[not found] ` <20210823113140.eEfFBnRXvMHfbVZf1oicrUjNF6ySBWIjnkJgGS2CcnM@z>
2021-08-23 11:31 ` [PATCH RFC v4 3/4] btrfs: use latest_dev in btrfs_show_devname Anand Jain
[not found] ` <20210823113141.Y4D53vkx_Zbqje2755YC8T5gXoihAWYX9bIUegUFgTQ@z>
2021-08-23 11:31 ` [PATCH v4 4/4] btrfs: update latest_dev when we sprout Anand Jain
2021-08-23 11:31 ` [PATCH v4 2/4] btrfs: save latest btrfs_device instead of its block_device in fs_devices Anand Jain
2021-08-23 11:45 ` [PATCH v3 0/4] btrf_show_devname related fixes David Sterba
2021-08-23 19:46 ` David Sterba [this message]
2021-08-24 0:28 ` [PATCH v4 " Anand Jain
2021-08-24 16:11 ` David Sterba
2021-08-25 2:13 ` Anand Jain
2021-08-31 15:40 ` David Sterba
2021-09-01 8:18 ` Anand Jain
2021-09-01 16:16 ` 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=20210823194618.GT5047@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=l@damenly.su \
--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 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).