diff options
author | Javier González <jg@lightnvm.io> | 2017-07-28 15:13:16 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2017-07-28 16:06:00 +0200 |
commit | 75cb8e939cf30ebdfffd9b28566d8aead95138a8 (patch) | |
tree | 867ba4c5211487b1aa5907302054efc7bead8ec4 /drivers/block | |
parent | Merge branch 'nvme-4.13' of git://git.infradead.org/nvme into for-linus (diff) | |
download | linux-75cb8e939cf30ebdfffd9b28566d8aead95138a8.tar.xz linux-75cb8e939cf30ebdfffd9b28566d8aead95138a8.zip |
lightnvm: pblk: advance bio according to lba index
When a lba either hits the cache or corresponds to an empty entry in the
L2P table, we need to advance the bio according to the position in which
the lba is located. Otherwise, we will copy data in the wrong page, thus
causing data corruption for the application.
In case of a cache hit, we assumed that bio->bi_iter.bi_idx would
contain the correct index, but this is no necessarily true. Instead, use
the local bio advance counter and iterator. This guarantees that lbas
hitting the cache are copied into the right bv_page.
In case of an empty L2P entry, we omitted to advance the bio. In the
cases when the same I/O also contains a cache hit, data corresponding
to this lba will be copied to the wrong bv_page. Fix this by advancing
the bio as we do in the case of a cache hit.
Fixes: a4bd217b4326 lightnvm: physical block device (pblk) target
Signed-off-by: Javier González <javier@javigon.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/block')
0 files changed, 0 insertions, 0 deletions