summaryrefslogtreecommitdiffstats
path: root/Kconfig
diff options
context:
space:
mode:
authorIgor Konopko <igor.j.konopko@intel.com>2018-12-11 20:16:27 +0100
committerJens Axboe <axboe@kernel.dk>2018-12-11 12:22:35 -0700
commit2c4d5356e64d7d538f24c23045478330fae4a065 (patch)
tree87d4d7172cf6de069f4d2fc0a9de4ffad7b12c59 /Kconfig
parent55d8ec35398e7ab001989473cf6ed6f40b5ef4a6 (diff)
downloadlinux-2c4d5356e64d7d538f24c23045478330fae4a065.tar.gz
linux-2c4d5356e64d7d538f24c23045478330fae4a065.tar.bz2
linux-2c4d5356e64d7d538f24c23045478330fae4a065.zip
lightnvm: pblk: do not overwrite ppa list with meta list
Ehen using pblk with 0 sized metadata both ppa list and meta list points to the same memory since pblk_dma_meta_size() returns 0 in that case. This patch fix that issue by ensuring that pblk_dma_meta_size() always returns space equal to sizeof(struct pblk_sec_meta) and thus ppa list and meta list points to different memory address. Even that in that case drive does not really care about meta_list pointer, this is the easiest way to fix that issue without introducing changes in many places in the code just for 0 sized metadata case. The same approach needs to be also done for pblk_get_sec_meta() since we also cannot point to the same memory address in meta buffer when we are using it for pblk recovery process Reported-by: Hans Holmberg <hans.holmberg@cnexlabs.com> Tested-by: Hans Holmberg <hans.holmberg@cnexlabs.com> Signed-off-by: Igor Konopko <igor.j.konopko@intel.com> Signed-off-by: Matias Bjørling <mb@lightnvm.io> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions