diff options
| author |   Keith Busch <keith.busch@intel.com> | 2016-02-24 09:15:58 -0700 |
|---|---|---|
| committer |   Jens Axboe <axboe@fb.com> | 2016-03-03 14:42:50 -0700 |
| commit | e9fc63d682dbbef17921aeb00d03fd52d6735ffd (patch) | |
| tree | 33d5f3ece18a1724ad42b79a7c4970859efca5e8 /fs/fs-writeback.c | |
| parent | NVMe: Don't allow unsupported flags (diff) | |
| download | wireguard-linux-e9fc63d682dbbef17921aeb00d03fd52d6735ffd.tar.xz wireguard-linux-e9fc63d682dbbef17921aeb00d03fd52d6735ffd.zip | |
NVMe: Fix 0-length integrity payload
A user could send a passthrough IO command with a metadata pointer to a
namespace without metadata. With metadata length of 0, kmalloc returns
ZERO_SIZE_PTR. Since that is not NULL, the driver would have set this as
the bio's integrity payload, which causes an access fault on completion.
This patch ignores the users metadata buffer if the namespace format
does not support separate metadata.
Reported-by: Stephen Bates <stephen.bates@microsemi.com>
Signed-off-by: Keith Busch <keith.busch@intel.com>
Reviewed-by: Sagi Grimberg <sagig@mellanox.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'fs/fs-writeback.c')
0 files changed, 0 insertions, 0 deletions