mtip32xx: Abort I/O during secure erase operation
authorAsai Thambi SP <asamymuthupa@micron.com>
Mon, 11 May 2015 22:51:27 +0000 (15:51 -0700)
committerJens Axboe <axboe@fb.com>
Tue, 16 Jun 2015 14:24:47 +0000 (08:24 -0600)
Currently I/Os are being queued when secure erase operation starts, and issue
them after the operation completes. As all data will be gone when the operation
completes, any queued I/O doesn't make sense. Hence, abort I/O (return -ENODATA)
as soon as the driver receives.

Signed-off-by: Selvan Mani <smani@micron.com>
Signed-off-by: Asai Thambi S P <asamymuthupa@micron.com>
Signed-off-by: Jens Axboe <axboe@fb.com>

No differences found