diff options
author | Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com> | 2019-06-11 15:10:17 -0700 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2019-06-13 03:00:30 -0600 |
commit | 154085ffdcc6875851b80a5d2bd759bbf687b001 (patch) | |
tree | 8d1a44bd6fb4c245adba7508721ff2881f944dee /samples | |
parent | 6cfc0081b046ebf50dd38c38e688c8de143614f3 (diff) | |
download | linux-154085ffdcc6875851b80a5d2bd759bbf687b001.tar.bz2 |
null_blk: remove duplicate check for report zone
This patch removes the check in the null_blk_zoned for report zone
command, where it checks for the dev-,>zoned before executing the report
zone.
The null_zone_report() function is a block_device operation callback
which is initialized in the null_blk_main.c and gets called as a part
of blkdev for report zone IOCTL (BLKREPORTZONE).
blkdev_ioctl()
blkdev_report_zones_ioctl()
blkdev_report_zones()
blk_report_zones()
disk->fops->report_zones()
nullb_zone_report();
The null_zone_report() will never get executed on the non-zoned block
device, in the non zoned block device blk_queue_is_zoned() will always
be false which is first check the blkdev_report_zones_ioctl()
before actual low level driver report zone callback is executed.
Here is the detailed scenario:-
1. modprobe null_blk
null_init
null_alloc_dev
dev->zoned = 0
null_add_dev
dev->zoned == 0
so we don't set the q->limits.zoned = BLK_ZONED_HR
2. blkzone report /dev/nullb0
blkdev_ioctl()
blkdev_report_zones_ioctl()
blk_queue_is_zoned()
blk_queue_is_zoned
q->limits.zoned == 0
return false
if (!blk_queue_is_zoned(q)) <--- true
return -ENOTTY;
Reviewed-by: Damien Le Moal <damien.lemoal@wdc.com>
Reviewed-by: Bob Liu <bob.liu@oracle.com>
Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions