WSL2-Linux-Kernel/drivers/block/null_blk
Christoph Hellwig c3d8edb170 null_blk: don't cap max_hw_sectors to BLK_DEF_MAX_SECTORS
[ Upstream commit 9a9525de865410047fa962867b4fcd33943b206f ]

null_blk has some rather odd capping of the max_hw_sectors value to
BLK_DEF_MAX_SECTORS, which doesn't make sense - max_hw_sector is the
hardware limit, and BLK_DEF_MAX_SECTORS despite the confusing name is the
default cap for the max_sectors field used for normal file system I/O.

Remove all the capping, and simply leave it to the block layer or
user to take up or not all of that for file system I/O.

Fixes: ea17fd354c ("null_blk: Allow controlling max_hw_sectors limit")
Signed-off-by: Christoph Hellwig <hch@lst.de>
Link: https://lore.kernel.org/r/20231227092305.279567-2-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2024-01-25 14:52:40 -08:00
..
Kconfig
Makefile
main.c null_blk: don't cap max_hw_sectors to BLK_DEF_MAX_SECTORS 2024-01-25 14:52:40 -08:00
null_blk.h for-5.13/drivers-2021-04-27 2021-04-28 14:39:37 -07:00
trace.c
trace.h
zoned.c drivers/block/null_blk/main: Fix a double free in null_init. 2021-04-26 09:04:40 -06:00