On Tue, Jun 07, 2011 at 03:51:58PM -0700, Greg KH wrote:
> On Wed, Jun 08, 2011 at 12:31:27AM +0200, Stefan Priebe - Profihost AG wrote:
> > >>The vanilla kernel list tolds me to contact you directly.
> > >They did? For what?
> > Sorry if this is wrong. I asked there (linux-kernel@xxxxxxxxxxxxxxx)
> > who i should contact and they told me i should contact the kernel
> > maintainer for 2.6.32 to report it.
> >
> > >Stable kernel stuff should go to stable@xxxxxxxxxx, not to me directly.
> > >
> > >Anyway, is there a fix that should be added to the .32-stable tree
> > >somewhere for this issue?
> > The problem is that the fix was never applied to 2.6.32 as it needs
> > to get backported first.
> >
> > Redhat has backported the patch here:
> > https://bugzilla.redhat.com/show_bug.cgi?id=642680
> >
> > >I can apply patch 081003fff467ea0e727f66d5d435b4f473a789b3 to the tree,
> > >but could you verify that it resolves your issue first before I do that?
> > I would if someone can provide a backport for this fix. I tried it
> > myself but i'm not a kernel hacker nor a C man.
> >
> > At least i'm seeing exactly the behaviour described in the fix and
> > at the redhat bugzilla:
> > https://bugzilla.redhat.com/show_bug.cgi?id=642680
>
> Ok, but Red Hat doesn't have the backported patch there, so I don't have
> anything to go off of here :(
>
> I tried to backport the patch to 2.6.32, but it doesn't apply at all,
> and I don't see how to make it work either.
>
> Any XFS developers want to help out and provide a fix for this problem
> on the .32-stable kernel that I could apply?
I'm travelling for the next week and a half, so I won't be able to
get to it any time soon....
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
|