Re: Fix bad backport to stable v3.16+

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2019-05-22 at 16:30 +0000, Song Liu wrote:
> Hi, 
> 
> As reported by Thorsten Knabe <linux@xxxxxxxxxxxxxxxxx>. 
> 
> 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.

-- 
Ben Hutchings
Theory and practice are closer in theory than in practice - John Levine


Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux