diff options
| author | Jens Axboe <axboe@kernel.dk> | 2018-02-28 09:18:57 -0700 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2018-02-28 12:23:35 -0700 |
| commit | 24941b90e639df2bf467531601a15d792eaa6d6b (patch) | |
| tree | 4bbd03d26cd2b5676dc390b9d0ea8abd38b49900 /drivers/block/loop.c | |
| parent | sbitmap: use test_and_set_bit_lock()/clear_bit_unlock() (diff) | |
| download | linux-24941b90e639df2bf467531601a15d792eaa6d6b.tar.gz linux-24941b90e639df2bf467531601a15d792eaa6d6b.zip | |
null_blk: add 'requeue' fault attribute
Similarly to the support we have for testing/faking timeouts for
null_blk, this adds support for triggering a requeue condition.
Considering the issues around restart we've been seeing, this should be
a useful addition to the testing arsenal to ensure that we are handling
requeue conditions correctly.
This works for queue mode 1 (legacy request_fn based path) and 2 (blk-mq
path), as there's no good way to do requeue with a bio based driver.
This is similar to the timeout path. For the blk-mq path, we alternate
between passing back BLK_STS_RESOURCE and manually calling
blk_mq_requeue_request() in the driver. The former will hit the core
requeue path, while the latter exercises the IO scheduler requeue
path.
Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com>
Reviewed-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/block/loop.c')
0 files changed, 0 insertions, 0 deletions
