| From | Greg Kroah-Hartman <> | Subject | [PATCH 4.13 008/110] dm integrity: do not check integrity for failed read operations | Date | Tue, 3 Oct 2017 14:28:30 +0200 |
| |
4.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hyunchul Lee <cheol.lee@lge.com>
commit b7e326f7b7375392d06f9cfbc27a7c63181f69d7 upstream.
Even though read operations fail, dm_integrity_map_continue() calls integrity_metadata() to check integrity. In this case, just complete these.
This also makes it so read I/O errors do not generate integrity warnings in the kernel log.
Signed-off-by: Hyunchul Lee <cheol.lee@lge.com> Acked-by: Milan Broz <gmazyland@gmail.com> Acked-by: Mikulas Patocka <mpatocka@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
--- drivers/md/dm-integrity.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
--- a/drivers/md/dm-integrity.c +++ b/drivers/md/dm-integrity.c @@ -1697,7 +1697,11 @@ sleep: if (need_sync_io) { wait_for_completion_io(&read_comp); - integrity_metadata(&dio->work); + if (likely(!bio->bi_status)) + integrity_metadata(&dio->work); + else + dec_in_flight(dio); + } else { INIT_WORK(&dio->work, integrity_metadata); queue_work(ic->metadata_wq, &dio->work);
|