diff options
| author | Damien Le Moal <damien.lemoal@wdc.com> | 2016-11-11 14:53:26 +0900 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2016-11-14 13:16:42 -0700 |
| commit | c6463c651d7ab599a4878115723a5bcb6ae5b470 (patch) | |
| tree | bd28799ca575bccb68122445b81ae84b1da0c756 /drivers/scsi/sd_zbc.c | |
| parent | dbb3ab03563cbf0880b1801a238b3e3964e364a1 (diff) | |
| download | op-kernel-dev-c6463c651d7ab599a4878115723a5bcb6ae5b470.zip op-kernel-dev-c6463c651d7ab599a4878115723a5bcb6ae5b470.tar.gz | |
sd_zbc: Force use of READ16/WRITE16
Normally, sd_read_capacity sets sdp->use_16_for_rw to 1 based on the
disk capacity so that READ16/WRITE16 are used for large drives.
However, for a zoned disk with RC_BASIS set to 0, the capacity reported
through READ_CAPACITY may be very small, leading to use_16_for_rw not being
set and READ10/WRITE10 commands being used, even after the actual zoned disk
capacity is corrected in sd_zbc_read_zones. This causes LBA offset overflow for
accesses beyond 2TB.
As the ZBC standard makes it mandatory for ZBC drives to support
the READ16/WRITE16 commands anyway, make sure that use_16_for_rw is set.
Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
eviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'drivers/scsi/sd_zbc.c')
| -rw-r--r-- | drivers/scsi/sd_zbc.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/scsi/sd_zbc.c b/drivers/scsi/sd_zbc.c index 394ab49..92620c8 100644 --- a/drivers/scsi/sd_zbc.c +++ b/drivers/scsi/sd_zbc.c @@ -612,6 +612,10 @@ int sd_zbc_read_zones(struct scsi_disk *sdkp, if (ret) goto err; + /* READ16/WRITE16 is mandatory for ZBC disks */ + sdkp->device->use_16_for_rw = 1; + sdkp->device->use_10_for_rw = 0; + return 0; err: |
