From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, trinity@vger.kernel.org
Subject: Re: found a scenario for BUG at fs/ext4/super.c:804!
Date: Sat, 03 Aug 2013 17:36:38 +0200 [thread overview]
Message-ID: <51FD2386.2050309@gmx.de> (raw)
In-Reply-To: <51FD1758.40107@gmx.de>
forget to attach the back trace of the uML of an EXT3 est case :
tfoerste@n22 ~ $ gdb --core=/mnt/ramdisk/core /usr/local/bin/linux-v3.11-rc3-288-gabe0308 -n -batch -ex bt
warning: core file may not match specified executable file.
[New LWP 8384]
Core was generated by `/usr/local/bin/linux-v3.11-rc3-288-gabe0308 earlyprintk ubda=/home/tfoerste/vir'.
Program terminated with signal 6, Aborted.
#0 0xb7735424 in __kernel_vsyscall ()
#0 0xb7735424 in __kernel_vsyscall ()
#1 0x083a3185 in kill ()
#2 0x0807163d in uml_abort () at arch/um/os-Linux/util.c:93
#3 0x08071925 in os_dump_core () at arch/um/os-Linux/util.c:138
#4 0x080613a7 in panic_exit (self=0x85a1518 <panic_exit_notifier>, unused1=0, unused2=0x85d6ce0 <buf.15904>) at arch/um/kernel/um_arch.c:240
#5 0x0809a388 in notifier_call_chain (nl=0x0, val=0, v=0x85d6ce0 <buf.15904>, nr_to_call=-2, nr_calls=0x0) at kernel/notifier.c:93
#6 0x0809a4d3 in __atomic_notifier_call_chain (nr_calls=<optimized out>, nr_to_call=<optimized out>, v=<optimized out>, val=<optimized out>, nh=<optimized out>) at kernel/notifier.c:182
#7 atomic_notifier_call_chain (nh=0x85d6cc4 <panic_notifier_list>, val=0, v=0x85d6ce0 <buf.15904>) at kernel/notifier.c:191
#8 0x08400968 in panic (fmt=0x0) at kernel/panic.c:128
#9 0x08168632 in ext3_put_super (sb=0x650e0f50) at fs/ext3/super.c:453
#10 0x08101092 in generic_shutdown_super (sb=0x650e0f50) at fs/super.c:418
#11 0x0810205a in kill_block_super (sb=0x0) at fs/super.c:1028
#12 0x08100f2a in deactivate_locked_super (s=0x650e0f50) at fs/super.c:299
#13 0x08100fc1 in deactivate_super (s=0x650e0f50) at fs/super.c:324
#14 0x08118dec in mntfree (mnt=<optimized out>) at fs/namespace.c:891
#15 mntput_no_expire (mnt=0x0) at fs/namespace.c:929
#16 0x0811a2d5 in SYSC_umount (flags=<optimized out>, name=<optimized out>) at fs/namespace.c:1335
#17 SyS_umount (name=134543744, flags=0) at fs/namespace.c:1305
#18 0x0811a349 in SYSC_oldumount (name=<optimized out>) at fs/namespace.c:1347
#19 SyS_oldumount (name=134543744) at fs/namespace.c:1345
#20 0x080618e2 in handle_syscall (r=0x663f6bd4) at arch/um/kernel/skas/syscall.c:35
#21 0x08073c0d in handle_trap (local_using_sysemu=<optimized out>, regs=<optimized out>, pid=<optimized out>) at arch/um/os-Linux/skas/process.c:198
#22 userspace (regs=0x663f6bd4) at arch/um/os-Linux/skas/process.c:431
#23 0x0805e65c in fork_handler () at arch/um/kernel/process.c:160
#24 0x5a5a5a5a in ?? ()
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
WARNING: multiple messages have this Message-ID (diff)
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, trinity@vger.kernel.org
Subject: Re: found a scenario for BUG at fs/ext4/super.c:804!
Date: Sat, 03 Aug 2013 17:36:38 +0200 [thread overview]
Message-ID: <51FD2386.2050309@gmx.de> (raw)
In-Reply-To: <51FD1758.40107@gmx.de>
forget to attach the back trace of the uML of an EXT3 est case :
tfoerste@n22 ~ $ gdb --core=/mnt/ramdisk/core /usr/local/bin/linux-v3.11-rc3-288-gabe0308 -n -batch -ex bt
warning: core file may not match specified executable file.
[New LWP 8384]
Core was generated by `/usr/local/bin/linux-v3.11-rc3-288-gabe0308 earlyprintk ubda=/home/tfoerste/vir'.
Program terminated with signal 6, Aborted.
#0 0xb7735424 in __kernel_vsyscall ()
#0 0xb7735424 in __kernel_vsyscall ()
#1 0x083a3185 in kill ()
#2 0x0807163d in uml_abort () at arch/um/os-Linux/util.c:93
#3 0x08071925 in os_dump_core () at arch/um/os-Linux/util.c:138
#4 0x080613a7 in panic_exit (self=0x85a1518 <panic_exit_notifier>, unused1=0, unused2=0x85d6ce0 <buf.15904>) at arch/um/kernel/um_arch.c:240
#5 0x0809a388 in notifier_call_chain (nl=0x0, val=0, v=0x85d6ce0 <buf.15904>, nr_to_call=-2, nr_calls=0x0) at kernel/notifier.c:93
#6 0x0809a4d3 in __atomic_notifier_call_chain (nr_calls=<optimized out>, nr_to_call=<optimized out>, v=<optimized out>, val=<optimized out>, nh=<optimized out>) at kernel/notifier.c:182
#7 atomic_notifier_call_chain (nh=0x85d6cc4 <panic_notifier_list>, val=0, v=0x85d6ce0 <buf.15904>) at kernel/notifier.c:191
#8 0x08400968 in panic (fmt=0x0) at kernel/panic.c:128
#9 0x08168632 in ext3_put_super (sb=0x650e0f50) at fs/ext3/super.c:453
#10 0x08101092 in generic_shutdown_super (sb=0x650e0f50) at fs/super.c:418
#11 0x0810205a in kill_block_super (sb=0x0) at fs/super.c:1028
#12 0x08100f2a in deactivate_locked_super (s=0x650e0f50) at fs/super.c:299
#13 0x08100fc1 in deactivate_super (s=0x650e0f50) at fs/super.c:324
#14 0x08118dec in mntfree (mnt=<optimized out>) at fs/namespace.c:891
#15 mntput_no_expire (mnt=0x0) at fs/namespace.c:929
#16 0x0811a2d5 in SYSC_umount (flags=<optimized out>, name=<optimized out>) at fs/namespace.c:1335
#17 SyS_umount (name=134543744, flags=0) at fs/namespace.c:1305
#18 0x0811a349 in SYSC_oldumount (name=<optimized out>) at fs/namespace.c:1347
#19 SyS_oldumount (name=134543744) at fs/namespace.c:1345
#20 0x080618e2 in handle_syscall (r=0x663f6bd4) at arch/um/kernel/skas/syscall.c:35
#21 0x08073c0d in handle_trap (local_using_sysemu=<optimized out>, regs=<optimized out>, pid=<optimized out>) at arch/um/os-Linux/skas/process.c:198
#22 userspace (regs=0x663f6bd4) at arch/um/os-Linux/skas/process.c:431
#23 0x0805e65c in fork_handler () at arch/um/kernel/process.c:160
#24 0x5a5a5a5a in ?? ()
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next prev parent reply other threads:[~2013-08-03 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 17:58 found a scenario for BUG at fs/ext4/super.c:804! Toralf Förster
2013-05-30 18:06 ` Toralf Förster
2013-06-01 13:48 ` Toralf Förster
2013-06-01 15:00 ` Eric Sandeen
2013-06-01 15:27 ` Toralf Förster
2013-06-01 18:02 ` Toralf Förster
2013-07-06 9:38 ` Toralf Förster
2013-07-06 9:38 ` Toralf Förster
2013-08-03 14:44 ` Toralf Förster
2013-08-03 15:36 ` Toralf Förster [this message]
2013-08-03 15:36 ` Toralf Förster
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=51FD2386.2050309@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=trinity@vger.kernel.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.