summaryrefslogtreecommitdiffstats
path: root/certs/blacklist_hashes.c
diff options
context:
space:
mode:
authorJavier González <javier@cnexlabs.com>2017-10-13 14:46:22 +0200
committerJens Axboe <axboe@kernel.dk>2017-10-13 16:34:57 +0200
commita4809fee4e774fdf3296cc69c22ce6e6acef36b2 (patch)
tree6d0e2d6834b43dade6027d30f2fda792e00fe132 /certs/blacklist_hashes.c
parentlightnvm: pblk: use rqd->end_io for completion (diff)
downloadlinux-a4809fee4e774fdf3296cc69c22ce6e6acef36b2.tar.xz
linux-a4809fee4e774fdf3296cc69c22ce6e6acef36b2.zip
lightnvm: pblk: check lba sanity on read path
As part of pblk's recovery scheme, we store the lba mapped to each physical sector on the device's out-of-bound (OOB) area. On the read path, we can use this information to validate that the data being delivered to the upper layers corresponds to the lba being requested. The cost of this check is an extra copy on the DMA region on the device and an extra comparison in the host, given that (i) the OOB area is being read together with the data in the media, and (ii) the DMA region allocated for the ppa list can be reused for the metadata stored on the OOB area. Signed-off-by: Javier González <javier@cnexlabs.com> Signed-off-by: Matias Bjørling <m@bjorling.me> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'certs/blacklist_hashes.c')
0 files changed, 0 insertions, 0 deletions