All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable
@ 2017-03-28  4:41 Fam Zheng
  2017-03-28  7:14   ` kbuild test robot
  2017-03-30  2:37 ` Martin K. Petersen
  0 siblings, 2 replies; 7+ messages in thread
From: Fam Zheng @ 2017-03-28  4:41 UTC (permalink / raw)
  To: linux-kernel
  Cc: Martin K. Petersen, famz, linux-scsi, Laurence Oberman,
	James E.J. Bottomley

If device reports a small max_xfer_blocks and a zero opt_xfer_blocks, we
end up using BLK_DEF_MAX_SECTORS, which is wrong and r/w of that size
may get error.

Fixes: ca369d51b3e ("block/sd: Fix device-imposed transfer length limits")
Signed-off-by: Fam Zheng <famz@redhat.com>

---

v2: Fix granularity mismatch. [Martin]
---
 drivers/scsi/sd.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index fcfeddc..a5c7e67 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi/sd.c
@@ -2957,6 +2957,7 @@ static int sd_revalidate_disk(struct gendisk *disk)
 		rw_max = logical_to_sectors(sdp, sdkp->opt_xfer_blocks);
 	} else
 		rw_max = BLK_DEF_MAX_SECTORS;
+	rw_max = min_not_zero(rw_max, logical_to_sectors(sdp, dev_max));
 
 	/* Combine with controller limits */
 	q->limits.max_sectors = min(rw_max, queue_max_hw_sectors(q));
-- 
2.9.3

^ permalink raw reply related	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2017-03-31  4:05 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-28  4:41 [PATCH v2] sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable Fam Zheng
2017-03-28  7:14 ` kbuild test robot
2017-03-28  7:14   ` kbuild test robot
2017-03-30  2:37 ` Martin K. Petersen
2017-03-30  4:13   ` Fam Zheng
2017-03-30 15:30     ` Martin K. Petersen
2017-03-31  4:05       ` Fam Zheng

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.