summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorHans Holmberg <hans.holmberg@cnexlabs.com>2018-03-30 00:04:51 +0200
committerJens Axboe <axboe@kernel.dk>2018-03-29 17:29:09 -0600
commitd0ab0b1ab991f48fc1fb579490df397d5f819913 (patch)
tree26ccf194c81a0bd1598efa5401cc3126517a5423 /MAINTAINERS
parentcfe1c9e2e2a34ccaf2ba01d2c435d65207335ca1 (diff)
downloadlinux-d0ab0b1ab991f48fc1fb579490df397d5f819913.tar.bz2
lightnvm: pblk: check data lines version on recovery
As a preparation for future bumps of data line persistent storage versions, we need to start checking the emeta line version during recovery. Also slit up the current emeta/smeta version into two bytes (major,minor). Recovering lines with the same major number as the current pblk data line version must succeed. This means that any changes in the persistent format must be: (1) Backward compatible: if we switch back to and older kernel, recovery of lines stored with major == current_major and minor > current_minor must succeed. (2) Forward compatible: switching to a newer kernel, recovery of lines stored with major=current_major and minor < minor must handle the data format differences gracefully(i.e. initialize new data structures to default values). If we detect lines that have a different major number than the current we must abort recovery. The user must manually migrate the data in this case. Previously the version stored in the emeta header was copied from smeta, which has version 1, so we need to set the minor version to 1. Signed-off-by: Hans Holmberg <hans.holmberg@cnexlabs.com> Signed-off-by: Javier González <javier@cnexlabs.com> Signed-off-by: Matias Bjørling <mb@lightnvm.io> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions