summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorXiao Ni <xni@redhat.com>2019-03-08 23:52:05 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-03-19 13:12:42 +0100
commit27143c71d68be2b60b6f3800d312009158bc24e2 (patch)
tree8c2994f17b3adcd84e4fbbe33fb99396274bf214
parentd6b577c6201fe12bb33f15167623662f3c5f14d0 (diff)
downloadlinux-stable-27143c71d68be2b60b6f3800d312009158bc24e2.tar.gz
linux-stable-27143c71d68be2b60b6f3800d312009158bc24e2.tar.bz2
linux-stable-27143c71d68be2b60b6f3800d312009158bc24e2.zip
It's wrong to add len to sector_nr in raid10 reshape twice
commit b761dcf1217760a42f7897c31dcb649f59b2333e upstream. In reshape_request it already adds len to sector_nr already. It's wrong to add len to sector_nr again after adding pages to bio. If there is bad block it can't copy one chunk at a time, it needs to goto read_more. Now the sector_nr is wrong. It can cause data corruption. Cc: stable@vger.kernel.org # v3.16+ Signed-off-by: Xiao Ni <xni@redhat.com> Signed-off-by: Song Liu <songliubraving@fb.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r--drivers/md/raid10.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
index 7033a2880771..9df1334608b7 100644
--- a/drivers/md/raid10.c
+++ b/drivers/md/raid10.c
@@ -4630,7 +4630,6 @@ read_more:
atomic_inc(&r10_bio->remaining);
read_bio->bi_next = NULL;
generic_make_request(read_bio);
- sector_nr += nr_sectors;
sectors_done += nr_sectors;
if (sector_nr <= last)
goto read_more;