On 01/27/2014 07:02 PM, Guillaume Morin wrote:
On 27 Jan 16:28, Greg KH wrote:
I have verified commit 27c73ae759774e63313c1fbfeb17ba076cea64c5 indeed
fixes this bug. I have backported this fix to 3.4. I will run some more
tests and then I can send it out for 3.4 stable. Patch from upstream
commit may apply cleanly to 3.10 and 3.12 but I can check and backport
if needed.
If you could verify a simple "patch -p1" will properly fix the issue on
3.10 and 3.12, that would be greatly appreciated.
I have verified that 27c73ae759774e63313c1fbfeb17ba076cea64c5 applies
cleanly on 3.12.9. It applies on 3.10.28 as well (with some harmless
line offset warnings)
I have also verified this commit does fix the problem for these 2
kernels (as Khalid mentioned).
So looks like we're good to go for 3.10 and 3.12. I'll test Khalid's
patch for 3.4 when it's available.
I just sent out backported patch for 3.4. I also verified the upstream
commit does apply to stable 3.10 and 3.12 without any changes which
Guillaume has verified as well.
--
Khalid
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html