On Wed, Dec 19, 10:25, Dave Chinner wrote: > AFAIK 3.6 is still being updated - 3.6.11 was tagged only 29 hours ago. Quoting from the 3.6.11 release announcement: Note, this is the LAST kernel in the 3.6.y series, it is now end-of-life. Please move to the 3.7.y kernel series at this time. > I probably should also mention in the commit message that there is > no equivalent upstream fix, as the fix in 3.8 is part of a complete > reworking of the code and hence not appropriate for backporting > to -stable. Definitely. Greg tends to get grumpy when he is asked to apply a patch for the stable series that has no counterpart upstream :) > > > - if (!(mp->m_super->s_flags & MS_ACTIVE) && > > > > appears to be in the longterm kernels 3.2.35 and 3.4.24 as well (it > > was changed in commit 1307bbd which got reverted in 11159a05). Are > > these kernels also affected? > > I have no idea - I don't track them, don't test them and haven't > tried to reproduce the problem on them. > > If you want to support all the stable trees, you're welcome to do > all this, but it's not something I care to do. We have reports of > this problem on 3.5 to 3.7 and the patch applies to all three > kernels, so that's as far as I care right now.... Understood. Personally, I only care about 3.4 as this is the kernel we are running on most of our production systems. Would you be willing to submit the patch also for 3.4-stable if Matthias or myself reproduced the issue on 3.4 and confirmed that the patch fixes the problem there as well? Thanks Andre -- The only person who always got his work done by Friday was Robinson Crusoe
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
