From: Douglas Gilbert Date: Fri, 9 Sep 2005 10:07:32 +0000 (+1000) Subject: [SCSI] permit READ DEFECT DATA in block/scsi_ioctl X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=942fc2fb73f2cac53484ebaf1c4f9af7aefaca83;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git [SCSI] permit READ DEFECT DATA in block/scsi_ioctl The soon to be released smartmontools 5.34 uses the READ DEFECT DATA command on SCSI disks. A disk that has defect list entries (or worse, an increasing number of them) is at risk. Currently the first invocation of smartctl causes this: scsi: unknown opcode 0x37 message to appear the console and in the log. The READ DEFECT DATA SCSI command does not change the state of a disk. Its opcode (0x37) is valid for SBC devices (e.g. disks) and SMC-2 devices (media changers) where it is called INITIALIZE STATUS ELEMENT WITH RANGE and again doesn't change the external state of the device. Changelog: - mark SCSI opcode 0x37 (READ DEFECT DATA) as safe_for_read Signed-off-by: Douglas Gilbert Acked-by: Jens Axboe Signed-off-by: James Bottomley --- diff --git a/drivers/block/scsi_ioctl.c b/drivers/block/scsi_ioctl.c index abb2df249fd3..856c2278e9d0 100644 --- a/drivers/block/scsi_ioctl.c +++ b/drivers/block/scsi_ioctl.c @@ -123,6 +123,7 @@ static int verify_command(struct file *file, unsigned char *cmd) safe_for_read(READ_12), safe_for_read(READ_16), safe_for_read(READ_BUFFER), + safe_for_read(READ_DEFECT_DATA), safe_for_read(READ_LONG), safe_for_read(INQUIRY), safe_for_read(MODE_SENSE),