linux-stable.git/drivers/lightnvm, branch linux-5.4.y

lightnvm: disable the subsystem

2022-05-09T07:03:20+00:00

In commit 9ea9b9c48387 ("remove the lightnvm subsystem") the lightnvm
subsystem was removed as there is no hardware in the wild for it, and
the code is known to have problems.  This should also be disabled for
older LTS kernels as well to prevent anyone from accidentally using it.

Cc: Christoph Hellwig 
Cc: Matias Bjørling 
Cc: Javier González 
Cc: Jens Axboe 
Signed-off-by: Greg Kroah-Hartman

lightnvm: fix memory leak when submit fails

2021-01-27T10:47:53+00:00

commit 97784481757fba7570121a70dd37ca74a29f50a8 upstream.

The allocated page is not released if error occurs in
nvm_submit_io_sync_raw(). __free_page() is moved ealier to avoid
possible memory leak issue.

Fixes: aff3fb18f957 ("lightnvm: move bad block and chunk state logic to core")
Signed-off-by: Pan Bian 
Signed-off-by: Jens Axboe 
Signed-off-by: Greg Kroah-Hartman

lightnvm: select CONFIG_CRC32

2021-01-17T13:05:37+00:00

commit 19cd3403cb0d522dd5e10188eef85817de29e26e upstream.

Without CRC32 support, this fails to link:

arm-linux-gnueabi-ld: drivers/lightnvm/pblk-init.o: in function `pblk_init':
pblk-init.c:(.text+0x2654): undefined reference to `crc32_le'
arm-linux-gnueabi-ld: drivers/lightnvm/pblk-init.o: in function `pblk_exit':
pblk-init.c:(.text+0x2a7c): undefined reference to `crc32_le'

Fixes: a4bd217b4326 ("lightnvm: physical block device (pblk) target")
Signed-off-by: Arnd Bergmann 
Signed-off-by: Jens Axboe 
Signed-off-by: Greg Kroah-Hartman

lightnvm: fix out-of-bounds write to array devices->info[]

2020-10-29T08:58:00+00:00

[ Upstream commit a48faebe65b0db55a73b9220c3d919eee849bb79 ]

There is an off-by-one array check that can lead to a out-of-bounds
write to devices->info[i].  Fix this by checking by using >= rather
than > for the size check. Also replace hard-coded array size limit
with ARRAY_SIZE on the array.

Addresses-Coverity: ("Out-of-bounds write")
Fixes: cd9e9808d18f ("lightnvm: Support for Open-Channel SSDs")
Signed-off-by: Colin Ian King 
Signed-off-by: Jens Axboe 
Signed-off-by: Sasha Levin

lightnvm: print error when target is not found

2019-09-05T19:17:01+00:00

If userspace requests target to be removed, nvm_remove_tgt() will
iterate the nvm_devices to find out the given target, but if not
found, then it should print out an error.

Signed-off-by: Minwoo Im 
Updated output string and patch description.
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: introduce pr_fmt for the prefix nvm

2019-09-05T19:16:59+00:00

all the pr_() family can have this prefix by pr_fmt.

Signed-off-by: Minwoo Im 
Reviewed-by: Javier González 
Signed-off-by: Matias Bjørling 
Signed-off-by: Jens Axboe

lightnvm: remove unused 'geo' variable

2019-08-09T04:14:04+00:00

A previous commit correctly removed set-but-not-read variables, but
this left two new variables now unused. Kill them.

Fixes: ba6f7da99aaf ("lightnvm: remove set but not used variables 'data_len' and 'rq_len'")
Reported-by: Stephen Rothwell 
Signed-off-by: Jens Axboe

lightnvm: remove set but not used variables 'data_len' and 'rq_len'

2019-08-08T13:34:34+00:00

drivers/lightnvm/pblk-read.c: In function pblk_submit_read_gc:
drivers/lightnvm/pblk-read.c:423:6: warning: variable data_len set but not used [-Wunused-but-set-variable]
drivers/lightnvm/pblk-recovery.c: In function pblk_recov_scan_oob:
drivers/lightnvm/pblk-recovery.c:368:15: warning: variable rq_len set but not used [-Wunused-but-set-variable]

They are not used since commit 48e5da725581 ("lightnvm:
move metadata mapping to lower level driver")

Reported-by: Hulk Robot 
Signed-off-by: YueHaibing 
Signed-off-by: Jens Axboe

lightnvm: pblk: use kvmalloc for metadata

2019-08-06T14:20:10+00:00

There is no reason now not to use kvmalloc, so replace the internal
metadata allocation scheme.

Reviewed-by: Javier González 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Hans Holmberg 
Signed-off-by: Jens Axboe

lightnvm: move metadata mapping to lower level driver

2019-08-06T14:20:10+00:00

Now that blk_rq_map_kern can map both kmem and vmem, move internal
metadata mapping down to the lower level driver.

Reviewed-by: Javier González 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Hans Holmberg 
Signed-off-by: Jens Axboe