Christoph Hellwig 45686b6198 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>		2016-03-03 14:43:10 -07:00
..
core.c	nvme: fix max_segments integer truncation	2016-03-03 14:43:10 -07:00
Kconfig	nvme: fix Kconfig description for BLK_DEV_NVME_SCSI	2016-02-09 10:21:22 -07:00
lightnvm.c	lightnvm: check overflow and correct mlc pairs	2016-02-04 09:19:45 -07:00
Makefile	Merge branch 'for-4.5/nvme' of git://git.kernel.dk/linux-block	2016-01-21 19:58:02 -08:00
nvme.h	NVMe: Move error handling to failed reset handler	2016-03-03 14:42:50 -07:00
pci.c	NVMe: Move error handling to failed reset handler	2016-03-03 14:42:50 -07:00
scsi.c	nvme: move chardev and sysfs interface to common code	2015-12-01 10:59:40 -07:00