Christoph Hellwig 6e9429f9c6 null_blk: don't cap max_hw_sectors to BLK_DEF_MAX_SECTORS ... [ Upstream commit 9a9525de86 ] 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 15:27:30 -08:00
..
Kconfig	…
Makefile	…
main.c	null_blk: don't cap max_hw_sectors to BLK_DEF_MAX_SECTORS	2024-01-25 15:27:30 -08:00
null_blk.h	null_blk: add configfs variables for 2 options	2022-08-02 17:15:02 -06:00
trace.c	…
trace.h	treewide: Rename enum req_opf into enum req_op	2022-07-14 12:14:30 -06:00
zoned.c	treewide: Rename enum req_opf into enum req_op	2022-07-14 12:14:30 -06:00