diff options
| author | Nigel Croxon <ncroxon@redhat.com> | 2019-09-06 09:21:33 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-10-05 13:13:56 +0200 |
| commit | c5f89ff633d2aa2b20072969dcfdf4af960d1eba (patch) | |
| tree | 5144466e5be712bd71ba69f1d5235c10390e0299 /drivers/mmc | |
| parent | 7cb4bc790e12563b7f623485eb5f159e8b482cd5 (diff) | |
| download | linux-stable-c5f89ff633d2aa2b20072969dcfdf4af960d1eba.tar.gz linux-stable-c5f89ff633d2aa2b20072969dcfdf4af960d1eba.tar.bz2 linux-stable-c5f89ff633d2aa2b20072969dcfdf4af960d1eba.zip | |
raid5: don't increment read_errors on EILSEQ return
[ Upstream commit b76b4715eba0d0ed574f58918b29c1b2f0fa37a8 ]
While MD continues to count read errors returned by the lower layer.
If those errors are -EILSEQ, instead of -EIO, it should NOT increase
the read_errors count.
When RAID6 is set up on dm-integrity target that detects massive
corruption, the leg will be ejected from the array. Even if the
issue is correctable with a sector re-write and the array has
necessary redundancy to correct it.
The leg is ejected because it runs up the rdev->read_errors beyond
conf->max_nr_stripes. The return status in dm-drypt when there is
a data integrity error is -EILSEQ (BLK_STS_PROTECTION).
Signed-off-by: Nigel Croxon <ncroxon@redhat.com>
Signed-off-by: Song Liu <songliubraving@fb.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/mmc')
0 files changed, 0 insertions, 0 deletions