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 /block | |
| parent | 84fca1b0c461e741268fe947f641296c0d963a56 (diff) | |
| download | linux-stable-c04fa44b76b8d9d4f6b577030aa0cbb20359c428.tar.gz linux-stable-c04fa44b76b8d9d4f6b577030aa0cbb20359c428.tar.bz2 linux-stable-c04fa44b76b8d9d4f6b577030aa0cbb20359c428.zip | |
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 'block')
| -rw-r--r-- | block/blk-core.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/block/blk-core.c b/block/blk-core.c index 3f56be15f17e..cf0ee764b908 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -2220,10 +2220,10 @@ static inline int blk_partition_remap(struct bio *bio) if (bio_check_eod(bio, part_nr_sects_read(p))) goto out; bio->bi_iter.bi_sector += p->start_sect; - bio->bi_partno = 0; trace_block_bio_remap(bio->bi_disk->queue, bio, part_devt(p), bio->bi_iter.bi_sector - p->start_sect); } + bio->bi_partno = 0; ret = 0; out: rcu_read_unlock(); |