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, 24 Apr 2020 06:00:25 +0000 (08:00 +0200)
commit063ec77ac61b1990796f70f05ee1df352bd8461b
tree1a48b4d2898d10ebf8a70033e18af3ae204e4940
parentdf92d602b7305702bb784f83db4c0ccb125a5a17
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.c