From: Andrew Morton <akpm@osdl.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, sct@redhat.com,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.15-git7 oopses in ext3 during LTP runs
Date: Wed, 11 Jan 2006 12:46:17 -0800 [thread overview]
Message-ID: <20060111124617.5e7e1eaa.akpm@osdl.org> (raw)
In-Reply-To: <200601112126.59796.ak@suse.de>
Andi Kleen <ak@suse.de> wrote:
>
>
> Running LTP with the default runfile on a 4 virtual CPU x86-64
> system gives
>
> To reproduce: run ltp 20040908 (newer one will probably work
> too) with runltp -p -q -l `uname -r` on a ext3 file system
>
> config is x86-64 defconfig.
>
mutex_trylock() is returning the wrong value. fs/super.c:write_super()
clearly took the lock.
Ingo, weren't you hitting this occasionally?
>
> ----------- [cut here ] --------- [please bite here ] ---------
> Kernel BUG at /home/lsrc/quilt/linux/fs/ext3/super.c:2154
> invalid opcode: 0000 [1] SMP
> CPU 0
> Modules linked in:
> Pid: 14055, comm: pdflush Not tainted 2.6.15-git7 #90
> RIP: 0010:[<ffffffff801d998e>] <ffffffff801d998e>{ext3_write_super+20}
> RSP: 0018:ffff810117fb1e08 EFLAGS: 00010202
> RAX: 0000000000000001 RBX: ffff81011f9ae800 RCX: ffffffff80492060
> RDX: 0000000000000000 RSI: ffff810117fb0000 RDI: ffff81011f9ae888
> RBP: ffff81011f9ae888 R08: ffff810117fb0000 R09: ffff810004f219e0
> R10: 0000000000000000 R11: 0000000000000002 R12: ffff81011f9ae870
> R13: ffffffff80159aee R14: ffff8100cdce1d68 R15: ffffffff80146b14
> FS: 0000000000000000(0000) GS:ffffffff8060d000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 00002aaaaab61000 CR3: 000000011baf3000 CR4: 00000000000006e0
> Process pdflush (pid: 14055, threadinfo ffff810117fb0000, task ffff81011fe5c400)
> Stack: ffff81011f9ae800 ffffffff8017aa43 0000000000000064 0000000000000000
> ffff8100cdce1d78 ffffffff801592f9 ffff81011fe5c400 ffffffff80494000
> 0000000000000000 0000000000000000
> Call Trace: <ffffffff8017aa43>{sync_supers+133} <ffffffff801592f9>{wb_kupdate+49}
> <ffffffff80159aee>{pdflush+0} <ffffffff80159c40>{pdflush+338}
> <ffffffff801592c8>{wb_kupdate+0} <ffffffff80146c7f>{kthread+203}
> <ffffffff801107ca>{child_rip+8} <ffffffff80146b14>{keventd_create_kthread+0}
> <ffffffff80146bb4>{kthread+0} <ffffffff801107c2>{child_rip+0}
>
> Code: 0f 0b 68 e9 0d 43 80 c2 6a 08 c6 43 21 00 5b c3 49 c7 c0 ca
> RIP <ffffffff801d998e>{ext3_write_super+20} RSP <ffff810117fb1e08>
> Badness in do_exit at /home/lsrc/quilt/linux/kernel/exit.c:796
>
> Call Trace: <ffffffff80136800>{do_exit+84} <ffffffff804024dd>{_spin_unlock_irqrestore+8}
> <ffffffff80146b14>{keventd_create_kthread+0} <ffffffff801114ef>{kernel_math_error+0}
> <ffffffff80159aee>{pdflush+0} <ffffffff80111c61>{do_invalid_op+163}
> <ffffffff801d998e>{ext3_write_super+20} <ffffffff8040116a>{thread_return+0}
> <ffffffff80110611>{error_exit+0} <ffffffff80146b14>{keventd_create_kthread+0}
> <ffffffff80159aee>{pdflush+0} <ffffffff801d998e>{ext3_write_super+20}
> <ffffffff801d998a>{ext3_write_super+16} <ffffffff8017aa43>{sync_supers+133}
> <ffffffff801592f9>{wb_kupdate+49} <ffffffff80159aee>{pdflush+0}
> <ffffffff80159c40>{pdflush+338} <ffffffff801592c8>{wb_kupdate+0}
> <ffffffff80146c7f>{kthread+203} <ffffffff801107ca>{child_rip+8}
> <ffffffff80146b14>{keventd_create_kthread+0} <ffffffff80146bb4>{kthread+0}
> <ffffffff801107c2>{child_rip+0}
next prev parent reply other threads:[~2006-01-11 20:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 20:26 Andi Kleen
2006-01-11 20:46 ` Andrew Morton [this message]
2006-01-11 20:55 ` Arjan van de Ven
2006-01-11 21:07 ` Andrew Morton
2006-01-11 21:27 ` Arjan van de Ven
2006-01-11 22:19 ` Ingo Molnar
2006-01-11 22:40 ` Pavel Machek
2006-01-11 22:44 ` David S. Miller
2006-01-12 0:30 ` Ingo Molnar
2006-01-11 22:47 ` Jesper Juhl
2006-01-12 8:51 ` Pavel Machek
2006-01-12 0:55 ` 2.6.15-git7 oopses in ext3 during LTP runs II - more problems Andi Kleen
2006-01-12 1:14 ` Andrew Morton
2006-01-12 1:25 ` Andi Kleen
2006-01-11 21:25 ` 2.6.15-git7 oopses in ext3 during LTP runs Jan Engelhardt
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=20060111124617.5e7e1eaa.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sct@redhat.com \
/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®