diff options
author | Jay Freyensee <james.p.freyensee@intel.com> | 2016-07-21 06:26:16 +0300 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2016-07-21 06:26:16 +0300 |
commit | fa9a89fc6637958594f285c8466422105e86e28c (patch) | |
tree | 5a5a12753d91cafc099e9cfcf43816a89fddbdcc /drivers/mmc | |
parent | f9cc4472c963e64493261d834155974c48c0ff88 (diff) | |
download | linux-fa9a89fc6637958594f285c8466422105e86e28c.tar.xz |
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>
Diffstat (limited to 'drivers/mmc')
0 files changed, 0 insertions, 0 deletions