md/raid5: Fix Force reconstruct-write io stuck in degraded raid5
authorChangSyun Peng <allenpeng@synology.com>
Fri, 31 Jul 2020 09:50:17 +0000 (17:50 +0800)
committerSong Liu <songliubraving@fb.com>
Mon, 3 Aug 2020 06:54:25 +0000 (23:54 -0700)
commita1c6ae3d9f3dd6aa5981a332a6f700cf1c25edef
tree24a23854defd0f5f4d2f93d9aa0cd880856680f7
parent3a31cf3d210f85d57fd302d83514832ebacb3ca7
md/raid5: Fix Force reconstruct-write io stuck in degraded raid5

In degraded raid5, we need to read parity to do reconstruct-write when
data disks fail. However, we can not read parity from
handle_stripe_dirtying() in force reconstruct-write mode.

Reproducible Steps:

1. Create degraded raid5
mdadm -C /dev/md2 --assume-clean -l5 -n3 /dev/sda2 /dev/sdb2 missing
2. Set rmw_level to 0
echo 0 > /sys/block/md2/md/rmw_level
3. IO to raid5

Now some io may be stuck in raid5. We can use handle_stripe_fill() to read
the parity in this situation.

Cc: <stable@vger.kernel.org> # v4.4+
Reviewed-by: Alex Wu <alexwu@synology.com>
Reviewed-by: BingJing Chang <bingjingc@synology.com>
Reviewed-by: Danny Shih <dannyshih@synology.com>
Signed-off-by: ChangSyun Peng <allenpeng@synology.com>
Signed-off-by: Song Liu <songliubraving@fb.com>
drivers/md/raid5.c