From: Andrew Morton <akpm@digeo.com>
To: Alexander Hoogerhuis <alexh@ihatent.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [BUG] 2.5.65-mm3 kernel BUG at fs/ext3/super.c:1795!
Date: Fri, 21 Mar 2003 12:39:19 -0800 [thread overview]
Message-ID: <20030321123919.0b8b1b86.akpm@digeo.com> (raw)
In-Reply-To: <8765qchhgo.fsf@lapper.ihatent.com>
Alexander Hoogerhuis <alexh@ihatent.com> wrote:
>
> Andrew Morton <akpm@digeo.com> writes:
> >
> > [SNIP]
> >
>
> Disk I/O on my machine froze up during very light work after a few
> hours, luckily I had a window open on another machine so I could do a
> simple capture and save the info:
>
> kernel BUG at fs/ext3/super.c:1795!
> invalid operand: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c018b522>] Not tainted VLI
> EFLAGS: 00010246
> EIP is at ext3_write_super+0x36/0x94
> eax: 00000000 ebx: c8834000 ecx: efb5904c edx: efb59000
> esi: efb59000 edi: c8834000 ebp: c8835ecc esp: c8835ec0
> ds: 007b es: 007b ss: 0068
> Process pdflush (pid: 7853, threadinfo=c8834000 task=ed0a5880)
> Stack: c8835ee4 00000287 efb5904c c8835ee4 c0153148 efb59000 00000077 51eb851f
> c8835fcc c8835fa4 c0137fd0 c03892fc 007b9f47 007b168f 00000000 00000000
> c8835ef4 00000000 00000001 00000000 00000001 00000000 00000053 00000000
> Call Trace:
> [<c0153148>] sync_supers+0xde/0xea
> [<c0137fd0>] wb_kupdate+0x68/0x161
> [<c0118985>] schedule+0x1a4/0x3ac
> [<c01386e8>] __pdflush+0xdc/0x1d8
> [<c01387e4>] pdflush+0x0/0x15
> [<c01387f5>] pdflush+0x11/0x15
> [<c0137f68>] wb_kupdate+0x0/0x161
> [<c0108e69>] kernel_thread_helper+0x5/0xb
How on earth did you do that?
sync_supers() does lock_super, then calls ext3_write_super.
ext3_write_super() does a down_trylock() on sb->s_lock and goes BUG
if it acquired the lock.
So you've effectively done this:
down(&sem);
if (down_trylock(&sem))
BUG();
This can only be a random memory scribble, a hardware bug or a
preempt-related bug in down_trylock().
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-21 20:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 7:58 2.5.65-mm3 Andrew Morton
2003-03-21 10:58 ` 2.5.65-mm3 Alexander Hoogerhuis
2003-03-21 11:05 ` 2.5.65-mm3 Andrew Morton
2003-03-21 12:05 ` 2.5.65-mm3 Alexander Hoogerhuis
2003-03-21 15:23 ` [BUG] 2.5.65-mm3 kernel BUG at fs/ext3/super.c:1795! Alexander Hoogerhuis
2003-03-21 20:39 ` Andrew Morton [this message]
2003-03-22 2:55 ` Alexander Hoogerhuis
2003-03-21 20:15 ` 2.5.65-mm3 Seth Chandler
2003-03-21 20:17 ` 2.5.65-mm3 Robert Love
2003-03-22 12:38 ` 2.5.65-mm3 bad: scheduling while atomic! [SCSI] Alexander Hoogerhuis
2003-03-22 14:49 ` Alan Cox
2003-03-22 16:06 ` 2.5.65-mm2 vs 2.5.65-mm3 (full objrmap) Martin J. Bligh
2003-03-22 23:48 ` Hugh Dickins
2003-03-23 1:07 ` Martin J. Bligh
2003-03-23 8:14 ` Hugh Dickins
2003-03-23 8:56 ` William Lee Irwin III
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=20030321123919.0b8b1b86.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=alexh@ihatent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox