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-23 08:44:32 +0100
commitb83f73aa760899a492752f8447ec4ef230e5c01d (patch)
tree673b2613fd60cf1b8e93fd8c1a653a09bbc1ee96
parent9b37b964775e36ed742e112b7f44a91042c99a63 (diff)
downloadlinux-stable-b83f73aa760899a492752f8447ec4ef230e5c01d.tar.gz
linux-stable-b83f73aa760899a492752f8447ec4ef230e5c01d.tar.bz2
linux-stable-b83f73aa760899a492752f8447ec4ef230e5c01d.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 8d613652d0e2..98da5f5d847d 100644
--- a/drivers/md/raid10.c
+++ b/drivers/md/raid10.c
@@ -4442,7 +4442,6 @@ bio_full:
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;