null_blk: fix spurious IO errors after failed past-wp access
authorAlexey Dobriyan <adobriyan@gmail.com>
Wed, 12 Feb 2020 20:23:20 +0000 (23:23 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 17 Apr 2020 08:50:00 +0000 (10:50 +0200)
commit502b83e73e35163547117448ce6a0f4eab6fc6a6
tree69b377ae044619d46c07c10bf680ffd909fbf6a5
parent38c1299f8c5c0a1e8b1328b5e58dc1a19d567251
null_blk: fix spurious IO errors after failed past-wp access

[ Upstream commit ff77042296d0a54535ddf74412c5ae92cb4ec76a ]

Steps to reproduce:

BLKRESETZONE zone 0

// force EIO
pwrite(fd, buf, 4096, 4096);

[issue more IO including zone ioctls]

It will start failing randomly including IO to unrelated zones because of
->error "reuse". Trigger can be partition detection as well if test is not
run immediately which is even more entertaining.

The fix is of course to clear ->error where necessary.

Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Alexey Dobriyan (SK hynix) <adobriyan@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/block/null_blk_main.c