linux/drivers/nvme/host
Jay Freyensee fa9a89fc66 nvme: initialize variable before logical OR'ing it
It is typically not good coding or secure coding practice
to logical OR a variable without an initialization value first.
Here on this line:

integrity.flags |= BLK_INTEGRITY_DEVICE_CAPABLE;

BLK_INTEGRITY_DEVICE_CAPABLE is being OR'ed to a member variable
never set to an initial value. This patch fixes that.

Signed-off-by: Jay Freyensee <james.p.freyensee@intel.com>
Reviewed-by: Ming Lin <ming.l@samsung.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@fb.com>
2016-07-20 21:26:16 -06:00
..
core.c nvme: initialize variable before logical OR'ing it 2016-07-20 21:26:16 -06:00
fabrics.c nvme-fabrics: add-remove ctrl repeat fix 2016-07-12 08:32:19 -07:00
fabrics.h nvme-fabrics: Remove tl_retry_count 2016-07-12 08:31:11 -07:00
Kconfig nvme-rdma: add a NVMe over Fabrics RDMA host driver 2016-07-08 08:38:49 -06:00
lightnvm.c block: get rid of bio_rw and READA 2016-07-20 17:37:01 -06:00
Makefile nvme-rdma: add a NVMe over Fabrics RDMA host driver 2016-07-08 08:38:49 -06:00
nvme.h nvme: Limit command retries 2016-07-12 16:20:31 -07:00
pci.c nvme: avoid crashes when node 0 is memoryless node. 2016-07-13 09:17:55 -07:00
rdma.c nvme-rdma: Don't use tl_retry_count 2016-07-12 08:31:10 -07:00
scsi.c nvme: move chardev and sysfs interface to common code 2015-12-01 10:59:40 -07:00