From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] kernel BUG at drivers/block/loop.c:621
Date: Fri, 17 Mar 2006 19:12:11 -0500 [thread overview]
Message-ID: <200603171912.12082.rob@landley.net> (raw)
I can reproduce the following in 2.6.16-rc5, User Mode Linux:
kernel BUG at drivers/block/loop.c:621!
Kernel panic - not syncing: BUG!
EIP: 0073:[<ffffe410>] CPU: 0 Not tainted ESP: 007b:b7de1f9c EFLAGS: 00200246
Not tainted
EAX: 00000000 EBX: 000018be ECX: 00000013 EDX: 000018be
ESI: 000018bb EDI: 00000011 EBP: b7de1fb8 DS: 007b ES: 007b
09b87bb4: [<0806c762>] show_regs+0x102/0x110
09b87bd0: [<0805b6fc>] panic_exit+0x2c/0x50
09b87be0: [<0807ff7d>] notifier_call_chain+0x2d/0x50
09b87c00: [<08071095>] panic+0x75/0x120
09b87c20: [<0812e181>] loop_thread+0x151/0x160
09b87c4c: [<08065297>] run_kernel_thread+0x37/0x60
09b87cfc: [<0805bbd1>] new_thread_handler+0x91/0xc0
09b87d20: [<ffffe420>] disks+0xf7e7ec84/0x4
The reproduction sequence is a bit involved (my mount regression test and the
current svn snapshot of busybox are involved), and running the following
sequence of commands:
mount; mount -a; mount; mount /dev/loop1 /images/vfat.dir ;
losetup /dev/loop1; ls; vi /etc/fstab; cat /etc/fstab; losetup /dev/loop0;
mount /images/vfat.img /images/vfat.dir -o ro
The current busybox mount is still broken in a couple of known places (hence
the testing; I'm fixing it). But it probably shouldn't panic the kernel...
Rob
--
Never bet against the cheap plastic solution.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: kernel BUG at drivers/block/loop.c:621
Date: Fri, 17 Mar 2006 19:12:11 -0500 [thread overview]
Message-ID: <200603171912.12082.rob@landley.net> (raw)
I can reproduce the following in 2.6.16-rc5, User Mode Linux:
kernel BUG at drivers/block/loop.c:621!
Kernel panic - not syncing: BUG!
EIP: 0073:[<ffffe410>] CPU: 0 Not tainted ESP: 007b:b7de1f9c EFLAGS: 00200246
Not tainted
EAX: 00000000 EBX: 000018be ECX: 00000013 EDX: 000018be
ESI: 000018bb EDI: 00000011 EBP: b7de1fb8 DS: 007b ES: 007b
09b87bb4: [<0806c762>] show_regs+0x102/0x110
09b87bd0: [<0805b6fc>] panic_exit+0x2c/0x50
09b87be0: [<0807ff7d>] notifier_call_chain+0x2d/0x50
09b87c00: [<08071095>] panic+0x75/0x120
09b87c20: [<0812e181>] loop_thread+0x151/0x160
09b87c4c: [<08065297>] run_kernel_thread+0x37/0x60
09b87cfc: [<0805bbd1>] new_thread_handler+0x91/0xc0
09b87d20: [<ffffe420>] disks+0xf7e7ec84/0x4
The reproduction sequence is a bit involved (my mount regression test and the
current svn snapshot of busybox are involved), and running the following
sequence of commands:
mount; mount -a; mount; mount /dev/loop1 /images/vfat.dir ;
losetup /dev/loop1; ls; vi /etc/fstab; cat /etc/fstab; losetup /dev/loop0;
mount /images/vfat.img /images/vfat.dir -o ro
The current busybox mount is still broken in a couple of known places (hence
the testing; I'm fixing it). But it probably shouldn't panic the kernel...
Rob
--
Never bet against the cheap plastic solution.
next reply other threads:[~2006-03-18 0:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-18 0:12 Rob Landley [this message]
2006-03-18 0:12 ` kernel BUG at drivers/block/loop.c:621 Rob Landley
2006-03-18 0:24 ` [uml-devel] " Blaisorblade
2006-03-18 0:24 ` Blaisorblade
2006-03-18 0:55 ` Rob Landley
2006-03-18 0:55 ` Rob Landley
2006-03-18 1:04 ` Blaisorblade
2006-03-18 1:04 ` Blaisorblade
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=200603171912.12082.rob@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.