mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: "Nathaniel W. Filardo" <nwf@andrew.cmu.edu>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] XFS crash using Realtime Preemption patch
Date: Thu, 23 Dec 2004 10:58:58 +1100	[thread overview]
Message-ID: <20041223105858.C702917@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.60-041.0412220246390.11361@unix49.andrew.cmu.edu>; from nwf@andrew.cmu.edu on Wed, Dec 22, 2004 at 02:50:20AM -0500

On Wed, Dec 22, 2004 at 02:50:20AM -0500, Nathaniel W. Filardo wrote:
> I added
>          BUG_ON( (mrp->mr_writer != 0) && (mrp->mr_writer != 1) );
> to mrlock.h : mrunlock() to see if it was corruption and got the following 

Good thinkin.

> instead.  It's a similar call pathway, but somewhat different.

Thats exactly the same call path right?  There is no call to
down_trylock from xfs_iunlock (goes directly to up_write) so
I think that must just be leftover stack junk, and we should
assume the path was xfs_iunlock->(inline)mrunlock->up_write,
which means your BUG_ON didn't trigger... (put a printk of the
value there, maybe we'll get lucky and get some recognisable
hex pattern).

> kernel BUG at kernel/rt.c:1210!
> invalid operand: 0000 [#1]
> PREEMPT
> Modules linked in: uhci_hcd rtc eth1394 ohci1394 ieee1394 pcmcia 
> hostap_pci hostap 8139too mii yenta_socket pcmcia_core ehci_hcd 
> i2c_ali15x3 i2c_core ohci_hcd usbcore tun crc32
> CPU:    0
> EIP:    0060:[<c01308ac>]    Not tainted VLI
> EFLAGS: 00010286   (2.6.10-rc3-mm1-V0.7.33-04-tcfq17)
> EIP is at up_write+0x8c/0xa0
> eax: 00000019   ebx: d039171c   ecx: 00000000   edx: 00000000
> esi: 00000008   edi: d039168c   ebp: 00000000   esp: cf8a6cdc
> ds: 007b   es: 007b   ss: 0068   preempt: 00000001
> Process rm (pid: 8661, threadinfo=cf8a6000 task=d5014370)
> Stack: c0357dbb c035a1f6 000004ba c0130ddf 00000010 00000286 d039171c 
> c01d2d8c
>         cf8a6000 d038dec8 d020bb44 d039168c d038dec8 d020bb44 c01d735c 
> cf8a6d38
>         cf8a6d3c 00000000 00000000 d6c3eb4c 00000000 d6c3ec00 00000002 
> c7af1700
> Call Trace:
>   [<c0130ddf>] down_trylock+0x1f/0xb0 (16)
>   [<c01d2d8c>] xfs_iunlock+0x6c/0x130 (16)
>   [<c01d735c>] xfs_iflush+0x1cc/0x440 (28)

-- 
Nathan

  reply	other threads:[~2004-12-22 23:59 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
2004-12-22  7:50     ` Nathaniel W. Filardo
2004-12-22 23:58       ` Nathan Scott [this message]
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=20041223105858.C702917@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®