aboutsummaryrefslogtreecommitdiff
path: root/drivers/nvmem/stm32-romem.c
diff options
context:
space:
mode:
authorDamien Le Moal2023-03-22 11:22:11 +0900
committerGreg Kroah-Hartman2023-04-26 14:28:36 +0200
commit480df96832f484060b4740164685f56a2fada450 (patch)
treed5adb371d1c3c4c3d3146da727ee2b0ab85f8664 /drivers/nvmem/stm32-romem.c
parent83760e74ed1498167605abffd5c10fe0a3929ec4 (diff)
scsi: core: Improve scsi_vpd_inquiry() checks
[ Upstream commit f0aa59a33d2ac2267d260fe21eaf92500df8e7b4 ] Some USB-SATA adapters have broken behavior when an unsupported VPD page is probed: Depending on the VPD page number, a 4-byte header with a valid VPD page number but with a 0 length is returned. Currently, scsi_vpd_inquiry() only checks that the page number is valid to determine if the page is valid, which results in receiving only the 4-byte header for the non-existent page. This error manifests itself very often with page 0xb9 for the Concurrent Positioning Ranges detection done by sd_read_cpr(), resulting in the following error message: sd 0:0:0:0: [sda] Invalid Concurrent Positioning Ranges VPD page Prevent such misleading error message by adding a check in scsi_vpd_inquiry() to verify that the page length is not 0. Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com> Link: https://lore.kernel.org/r/20230322022211.116327-1-damien.lemoal@opensource.wdc.com Reviewed-by: Benjamin Block <bblock@linux.ibm.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/nvmem/stm32-romem.c')
0 files changed, 0 insertions, 0 deletions