[PATCH 6/6] nvme: track shared namespaces in a siblings list

[Sagi Grimberg]

>> Not sure what you mean, but I didn't mean to change any locking scheme,
>> just have the sibling list exist in struct block_device and call
>> nvme_ns_find_siblings as a fops callout when the bdev is created, driver
>> stays responsible for locking.
> 
> A common list with driver specific locking isn't going to work,
> we'll need block locking for using it for multipath decisions.

Didn't mean driver specific locking on the sibling list itself,
just on the sibling search. The sibling list should obviously have its
own locking. You have yet to reveal how the block layer should handle
the siblings, but I imagine you have some family representation, which
will have its own locking scheme to manage siblings/paths.