From: Nathan Scott <nathans@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Nathaniel W. Filardo" <nwf@andrew.cmu.edu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] XFS crash using Realtime Preemption patch
Date: Wed, 22 Dec 2004 09:32:42 +1100 [thread overview]
Message-ID: <20041222093242.B674830@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20041221104042.GA31843@elte.hu>; from mingo@elte.hu on Tue, Dec 21, 2004 at 11:40:43AM +0100
On Tue, Dec 21, 2004 at 11:40:43AM +0100, Ingo Molnar wrote:
>
> * Nathaniel W. Filardo <nwf@andrew.cmu.edu> wrote:
>
> > Hello all.
> >
> > Using 2.6.10-rc3-mm1-V0.7.33-04 and TCFQ ver 17, I get the following
> > crash while trying to sync the portage tree, though the system seems
> > stable under interactive load (read: an rm command went OK prior to
> > this crash).
> >
> > Machine is a 933MHz transmeta laptop with IDE disk.
> >
> > Any more information you need?
> > --nwf;
> >
> > kernel BUG at kernel/rt.c:1210!
>
> Seems like an XFS bug at first sight. The BUG() means that an up_write()
> was done while a down_read() was active for the lock. Does XFS really do
> this?
That should definately not happen. Something has gone wrong in
mrlock.h if so - or it could be the incore xfs_inode has been
trampled on, and the mrlock writer state has become inappropriately
set.. that would cause the wrong branch to be taken and we'd end
up with the situation you've described here.
cheers.
--
Nathan
next prev parent reply other threads:[~2004-12-21 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 1:28 Nathaniel W. Filardo
2004-12-21 10:40 ` Ingo Molnar
2004-12-21 22:20 ` Nathaniel W. Filardo
2004-12-21 22:32 ` Nathan Scott [this message]
2004-12-22 7:50 ` Nathaniel W. Filardo
2004-12-22 23:58 ` Nathan Scott
2004-12-24 3:27 ` Nathaniel W. Filardo
2004-12-24 3:33 ` Nathan Scott
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=20041222093242.B674830@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nwf@andrew.cmu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®