]> git.baikalelectronics.ru Git - kernel.git/commit
nvme: fix max_segments integer truncation
authorChristoph Hellwig <hch@lst.de>
Wed, 2 Mar 2016 17:07:12 +0000 (18:07 +0100)
committerJens Axboe <axboe@fb.com>
Thu, 3 Mar 2016 21:43:10 +0000 (14:43 -0700)
commit23b73f162766f4f43d1db8e0813a35e6e0adbe7b
tree5c752a162d53af164942242d217d4cf54a98afd8
parenta40b66f0656097113bf529b00b2ef6393669269a
nvme: fix max_segments integer truncation

The block layer uses an unsigned short for max_segments.  The way we
calculate the value for NVMe tends to generate very large 32-bit values,
which after integer truncation may lead to a zero value instead of
the desired outcome.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reported-by: Jeff Lien <Jeff.Lien@hgst.com>
Tested-by: Jeff Lien <Jeff.Lien@hgst.com>
Reviewed-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
drivers/nvme/host/core.c