projects / linux-2.6-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c01d656) | patch
lightnvm: do not protect block 0
authorJavier González <jg@lightnvm.io>
Mon, 28 Nov 2016 21:38:55 +0000 (22:38 +0100)
committerJens Axboe <axboe@fb.com>
Tue, 29 Nov 2016 15:01:17 +0000 (08:01 -0700)
commit9aa1bc862b2fe1e6216c2448433a246d575aa11a
tree8ef1274d42b4d4034c09e9f752a688c0e1bd2b4ftree
parentc01d656eb1cba58820a4844f17bd71f5a4ef2c49commit | diff
lightnvm: do not protect block 0

Device blocks should be marked by the device and considered as bad
blocks by the media manager. Thus, do not make assumptions on which
blocks are going to be used by the device. In doing so we might lose
valid blocks from the free list.

Signed-off-by: Javier González <javier@cnexlabs.com>
Signed-off-by: Matias Bjørling <m@bjorling.me>
Signed-off-by: Jens Axboe <axboe@fb.com>
drivers/lightnvm/gennvm.c diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)