On Wed, Jul 11, 2018 at 05:22:06PM +0800, Anand Jain wrote:
> 
> Hi David,
> 
> Here I have put together a set of volume related patches which were
> sent to the ML as independent patches earlier. These have been
> reviewed and tested. Please pull.
> 
>   g...@github.com:asj/btrfs-devel.git misc-next-for-kdave

Sorry, the branch is not in a state so that I can pull, but thanks for
putting it together.

> [Anand:2]
> 6049bd5e9694 btrfs: add helper function check device delete able
> 8c96747831b0 btrfs: add helper btrfs_num_devices() to deduce num_devices
> dd61850ee7cf btrfs: warn for num_devices below 0
> 17c285ada2e4 btrfs: use the assigned fs_devices instead of the dereference
> e2f7c8a0f67b btrfs: do device clone using the btrfs_scan_one_device
> 89325c85d655 btrfs: fix race between free_stale_devices and close_fs_devices
> 0dfd68121520 btrfs: drop uuid_mutex in btrfs_free_extra_devids()
> 
> [David:2]
> 6fa6985bd169 btrfs: fix mount and ioctl device scan ioctl race
> e9f25a7b239d btrfs: reorder initialization before the mount locks uuid_mutex
> 2c5058cdf788 btrfs: lift uuid_mutex to callers of btrfs_parse_early_options
> 8ffc96e797bb btrfs: lift uuid_mutex to callers of btrfs_open_devices
> 39a2036c1d13 btrfs: lift uuid_mutex to callers of btrfs_scan_one_device
> 
> [Anand:1]
> e735e867d314 btrfs: fix btrfs_free_stale_devices() with needed locks
> bdc6cc879388 btrfs: btrfs_free_stale_devices() rename local variables
> 0dd1ff5cc6be btrfs: fix device_list_add() missing device_list_mutex()
> 622f0a7c31fe btrfs: do btrfs_free_stale_devices() outside of 
> device_list_add()
> 
> [David:1]
> 7302fc024079 btrfs: restore uuid_mutex in btrfs_open_devices
> 
> [Nikolay]
> 4da856347110 btrfs: drop pending list in device close

I'm going to add last 4 parts to misc-next as it fixes mkfs/mount races,
the remaining part is a mixed bag so I'll merge incrementall as reviewed
and a final patch versions land in the mailinglist.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to