From: Alex Riesen <alexander.riesen@synopsys.COM>
To: Burton Windle <bwindle@fint.org>
Cc: linux-kernel@vger.kernel.org, Matthew Wilcox <willy@debian.org>,
mdew@orcon.net.nz
Subject: Re: oops: 2.5.51 lock_get_status
Date: Fri, 13 Dec 2002 16:08:27 +0100 [thread overview]
Message-ID: <20021213150827.GA31448@riesen-pc.gr05.synopsys.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0212130942110.31117-100000@morpheus>
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:
> > > >
> >
next parent reply other threads:[~2002-12-13 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021213143115.GA30170@riesen-pc.gr05.synopsys.com>
[not found] ` <Pine.LNX.4.43.0212130942110.31117-100000@morpheus>
2002-12-13 15:08 ` Alex Riesen [this message]
2002-12-12 23:38 oops: 2.5.51 lock_get_status Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021213150827.GA31448@riesen-pc.gr05.synopsys.com \
--to=alexander.riesen@synopsys.com \
--cc=bwindle@fint.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdew@orcon.net.nz \
--cc=willy@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.