On Wed, May 22, 2019 at 04:30:33PM +0000, Song Liu wrote:

Hi,

As reported by Thorsten Knabe linux@thorsten-knabe.de.

commit 4f4fd7c5798b ("Don't jump to compute_result state from check_result state") was back ported to v3.16+. However, this fix was wrong.

Please back port the following two commits to fix this issue.

commit a25d8c327bb4 ("Revert "Don't jump to compute_result state from check_result state"") commit b2176a1dfb51 ("md/raid: raid5 preserve the writeback action after the parity check")

Added to 4.4+ for now.

thanks,

greg k-h

On Wed, 2019-05-22 at 16:30 +0000, Song Liu wrote:

Hi,

As reported by Thorsten Knabe linux@thorsten-knabe.de.

commit 4f4fd7c5798b ("Don't jump to compute_result state from check_result state") was back ported to v3.16+. However, this fix was wrong.

I never backported it to 3.16…

Please back port the following two commits to fix this issue.

commit a25d8c327bb4 ("Revert "Don't jump to compute_result state from check_result state"")

…so I didn't need this…

commit b2176a1dfb51 ("md/raid: raid5 preserve the writeback action after the parity check")

…but I have queued this up, thanks.

Ben.