linux-stable.git/drivers/block/null_blk.h, branch linux-5.6.y

null_blk: remove unused fields in 'nullb_cmd'

2020-02-25T16:43:29+00:00

'list', 'll_list' and 'csd' are no longer used.

The 'list' is not used since it was introduced by commit f2298c0403b0
("null_blk: multi queue aware block test driver").

The 'll_list' is no longer used since commit 3c395a969acc ("null_blk: set a
separate timer for each command").

The 'csd' is no longer used since commit ce2c350b2cfe ("null_blk: use
blk_complete_request and blk_mq_complete_request").

Reviewed-by: Bart Van Assche 
Signed-off-by: Dongli Zhang 
Signed-off-by: Jens Axboe

block: rework zone reporting

2019-11-13T02:12:07+00:00

Avoid the need to allocate a potentially large array of struct blk_zone
in the block layer by switching the ->report_zones method interface to
a callback model. Now the caller simply supplies a callback that is
executed on each reported zone, and private data for it.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Shin'ichiro Kawasaki 
Signed-off-by: Damien Le Moal 
Reviewed-by: Hannes Reinecke 
Reviewed-by: Mike Snitzer 
Signed-off-by: Jens Axboe

null_blk: clean up report zones

2019-11-13T02:12:01+00:00

Make the instance name match the method name and define the name to NULL
instead of providing an inline stub, which is rather pointless for a
method call.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Damien Le Moal 
Reviewed-by: Hannes Reinecke 
Reviewed-by: Chaitanya Kulkarni 
Signed-off-by: Jens Axboe

null_blk: return fixed zoned reads > write pointer

2019-10-18T01:01:22+00:00

A zoned block device maintains a write pointer within a zone, and reads
beyond the write pointer are undefined. Fill data buffer returned above
the write pointer with 0xFF.

Signed-off-by: Ajay Joshi 
Reviewed-by: Damien Le Moal 
Reviewed-by: Matias Bjørling 
Signed-off-by: Chaitanya Kulkarni 
Signed-off-by: Jens Axboe

null_blk: format pr_* logs with pr_fmt

2019-09-16T14:38:29+00:00

Instead of writing "null_blk: " at the beginning of each
pr_err/info/warn log message, format messages using pr_fmt() macro.

Reviewed-by: Chaitanya Kulkarni 
Signed-off-by: André Almeida 
Signed-off-by: Jens Axboe

null_blk: fix inline misuse

2019-08-23T18:49:00+00:00

You can't magically mark a function inline and expect that to work.

Fixes: fceb5d1b19cb ("null_blk: create a helper for zoned devices")
Signed-off-by: Jens Axboe

null_blk: create a helper for zoned devices

2019-08-23T12:58:05+00:00

This patch creates a helper function for handling zoned block device
operations.

This patch also restructured the code for null_blk_zoned.c and uses the
pattern to return blk_status_t and catch the error in the function
null_handle_cmd() into cmd->error variable instead of setting it up in
the deeper layer just like the way it is done for flush, badblocks and
memory backed case in the null_handle_cmd(). We also move
null_handle_zoned() to the null_blk_zoned.c to keep the zoned code
separate.

Signed-off-by: Chaitanya Kulkarni 
Signed-off-by: Jens Axboe

null_blk: fixup ->report_zones() for !CONFIG_BLK_DEV_ZONED

2019-07-12T15:09:57+00:00

A previous commit changed the prototype, but didn't adjust the function
for when zoned device support is disabled. Fix it up.

Fixes: bd976e527259 ("block: Kill gfp_t argument of blkdev_report_zones()")
Signed-off-by: Jens Axboe

block: Kill gfp_t argument of blkdev_report_zones()

2019-07-12T02:04:37+00:00

Only GFP_KERNEL and GFP_NOIO are used with blkdev_report_zones(). In
preparation of using vmalloc() for large report buffer and zone array
allocations used by this function, remove its "gfp_t gfp_mask" argument
and rely on the caller context to use memalloc_noio_save/restore() where
necessary (block layer zone revalidation and dm-zoned I/O error path).

Reviewed-by: Christoph Hellwig 
Reviewed-by: Martin K. Petersen 
Signed-off-by: Damien Le Moal 
Signed-off-by: Jens Axboe

null_blk: add zoned config support information

2019-01-06T17:58:27+00:00

If the kernel is built without CONFIG_BLK_DEV_ZONED, a modprobe
of the null_blk driver with zoned=1 fails with 'Invalid argument'.
This can be confusing to users, prompting a search as to why the
parameter is invalid. To assist in that search, add a bit more
information to the failure, additionally adding to the documentation
that CONFIG_BLK_DEV_ZONED is needed for zoned=1.

Reviewed-by: Bart Van Assche 
Signed-off-by: John Pittman 

Added null_blk prefix to error message.

Signed-off-by: Jens Axboe