Re: oops: 2.5.51 lock_get_status

Alex Riesen (alexander.riesen@synopsys.COM)
Fri, 13 Dec 2002 16:08:27 +0100


Burton Windle, Fri, Dec 13, 2002 15:42:20 +0100:
> This might also be of interest...
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=103825968004879&w=2
>

hmm... This:

| note, do not use NFS when using this patch. really; i mean it. somehow
| i managed to corrupt thread_info.cpu causing _udelay_ to oops.

doesn't look very encouraging.

Maybe there is already some news about it?
I volunteer to test anything :)
as being hit by the bug.

-alex

> On Fri, 13 Dec 2002, Alex Riesen wrote:
>
> > Burton Windle, Fri, Dec 13, 2002 15:08:45 +0100:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=16
> > >
> >
> > Oh, thanks. Still fogetting about the new thing to look before.
> >
> > > On Fri, 13 Dec 2002, Alex Riesen wrote:
> > >
> > > > 2.5.51+bk as of 12 Dec 23:00 CET.
> > > >
> > > > tried to strace(4.4) the d4x with follow-fork mode.
> > > > d4x is a multi-threaded app using posix advisory locks.
> > > > (http://www.krasu.ru/soft/chuchelo/)
> > > >
> > > > The thing calls fcntl, which fails as if the file were locked:
> > > >
> >
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/