diff options
author | Hannes Reinecke <hare@suse.de> | 2018-06-07 10:29:44 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2018-06-07 06:56:01 -0600 |
commit | c04fa44b76b8d9d4f6b577030aa0cbb20359c428 (patch) | |
tree | 7509f7ec032c0d913651a309f03542f5d900ef12 /include | |
parent | 84fca1b0c461e741268fe947f641296c0d963a56 (diff) | |
download | linux-c04fa44b76b8d9d4f6b577030aa0cbb20359c428.tar.bz2 |
block: always set partition number to '0' in blk_partition_remap()
blk_partition_remap() will only clear bi_partno if an actual remapping
has happened. But flush request et al don't have an actual size, so
the remapping doesn't happen and bi_partno is never cleared.
So for stacked devices blk_partition_remap() will be called on each level.
If (as is the case for native nvme multipathing) one of the lower-level
devices do _not_support partitioning a spurious I/O error is generated.
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions