nvme: don't use nvme_update_disk_info for the multipath disk
authorChristoph Hellwig <hch@lst.de>
Mon, 4 Mar 2024 14:04:51 +0000 (07:04 -0700)
committerKeith Busch <kbusch@kernel.org>
Mon, 4 Mar 2024 16:24:56 +0000 (08:24 -0800)
commit8f03cfa117e06bd2d3ba7ed8bba70a3dda310cae
tree558668ef733a156c54b8ceb3654906b783069f33
parent414c62e2ce5d93bfbdc12048530075dcea02cad8
nvme: don't use nvme_update_disk_info for the multipath disk

Currently nvme_update_ns_info_block calls nvme_update_disk_info both for
the namespace attached disk, and the multipath one (if it exists).  This
is very different from how other stacking drivers work, and leads to
a lot of complexity.

Switch to setting the disk capacity and initializing the integrity
profile, and let blk_stack_limits which already is called just below
deal with updating the other limits.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Keith Busch <kbusch@kernel.org>
drivers/nvme/host/core.c