Kernel bug reported in kern.log while trying to read corrupted ext3 filesystem

[John Wye]

Binary package hint: linux-image-2.6.20-15-generic

I use an IFS driver to access my ext3 Data partition on Windows. I keep my /home directory there, as well.
This driver managed to corrupt the filesystem while writing some files to it.

Obviously, I couldn't log on, but peeking in /var/log I found an error in parsing the Data filesystem.
Running fsck on the partition gave some error about an HTREE (?) and fixed the problem.

I wouldn't have reported this, but /var/log/kern.log talked about a kernel bug, and I suppose the error could have been handled more gracefully.

Here is the snippet of my /var/log/kern.log :

Jun 23 12:25:27 kubuntu kernel: [ 41.160322] /dev/vmnet: port on hub 8 successfully opened
Jun 23 12:25:29 kubuntu kernel: [ 43.565230] Assertion failure in dx_probe() at fs/ext3/namei.c:384: "dx_get_limit(entries) == dx_root_limit(dir, root->info.info_length)"
Jun 23 12:25:29 kubuntu kernel: [ 43.565278] ------------[ cut here ]------------
Jun 23 12:25:29 kubuntu kernel: [ 43.565284] kernel BUG at fs/ext3/namei.c:384!
Jun 23 12:25:29 kubuntu kernel: [ 43.565289] invalid opcode: 0000 [#1]
Jun 23 12:25:29 kubuntu kernel: [ 43.565293] SMP
Jun 23 12:25:29 kubuntu kernel: [ 43.565297] Modules linked in: binfmt_misc vmnet(P) vmmon(P) ppdev speedstep_lib cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_conservative tc1100_wmi pcc_acpi dev_acpi sony_acpi video sbs i2c_ec i2c_core dock button battery container ac asus_acpi backlight af_packet nls_iso8859_1 nls_cp437 vfat fat fuse sbp2 lp snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_util_mem snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_seq_device snd_pcm parport_pc parport snd_timer snd_page_alloc shpchp pci_hotplug snd soundcore psmouse intel_agp agpgart pcspkr serio_raw iTCO_wdt iTCO_vendor_support tsdev evdev ipv6 ext3 jbd mbcache sg sr_mod cdrom sd_mod usbhid hid ata_piix ata_generic libata scsi_mod ohci1394 ieee1394 e100 mii floppy generic ehci_hcd uhci_hcd usbcore thermal processor fan capability commoncap vesafb
Jun 23 12:25:29 kubuntu kernel: bcon tileblit font bitblit softcursor
Jun 23 12:25:29 kubuntu kernel: [ 43.565487] CPU: 0
Jun 23 12:25:29 kubuntu kernel: [ 43.565489] EIP: 0060:[<f8d45b51>] Tainted: P VLI
Jun 23 12:25:30 kubuntu kernel: [ 43.565493] EFLAGS: 00210292 (2.6.20-16-generic #2)
Jun 23 12:25:30 kubuntu kernel: [ 43.565513] EIP is at dx_probe+0x1e1/0x320 [ext3]
Jun 23 12:25:30 kubuntu kernel: [ 43.565519] eax: 00000090 ebx: f352e000 ecx: 00200096 edx: 00000000
Jun 23 12:25:30 kubuntu kernel: [ 43.565525] esi: f352e018 edi: f6126128 ebp: f353ec2c esp: f6813c74
Jun 23 12:25:30 kubuntu kernel: [ 43.565531] ds: 007b es: 007b ss: 0068
Jun 23 12:25:30 kubuntu kernel: [ 43.565537] Process kdm_greet (pid: 5510, ti=f6812000 task=dfd84560 task.ti=f6812000)
Jun 23 12:25:30 kubuntu kernel: [ 43.565543] Stack: f8d51f28 f8d5126b f8d53d6d 00000180 f8d52078 f6813d60 00000000 f7554b00
Jun 23 12:25:30 kubuntu kernel: [ 43.565557] 2d6b1158 f7ff2400 f6813d70 f6813d48 f6813e04 f8d4674b f6813d48 f6813d70
Jun 23 12:25:30 kubuntu kernel: [ 43.565571] 0000012f 00978002 f7ff2400 c01976cc 00001000 f79df090 f6813d44 c0188415
Jun 23 12:25:30 kubuntu kernel: [ 43.565585] Call Trace:
Jun 23 12:25:30 kubuntu kernel: [ 43.565638] [<f8d4674b>] ext3_find_entry+0x28b/0x640 [ext3]
Jun 23 12:25:30 kubuntu kernel: [ 43.565675] [__getblk+44/688] __getblk+0x2c/0x2b0
Jun 23 12:25:30 kubuntu kernel: [ 43.565696] [dput+181/320] dput+0xb5/0x140
Jun 23 12:25:30 kubuntu kernel: [ 43.565791] [<f8d40f0e>] __ext3_get_inode_loc+0x11e/0x340 [ext3]
Jun 23 12:25:30 kubuntu kernel: [ 43.565832] [__wake_up+56/80] __wake_up+0x38/0x50
Jun 23 12:25:30 kubuntu kernel: [ 43.565903] [<f8d4820c>] ext3_lookup+0x3c/0x100 [ext3]
Jun 23 12:25:30 kubuntu kernel: [ 43.565925] [d_alloc+263/400] d_alloc+0x107/0x190
Jun 23 12:25:30 kubuntu kernel: [ 43.565952] [do_lookup+328/400] do_lookup+0x148/0x190
Jun 23 12:25:30 kubuntu kernel: [ 43.565987] [__link_path_walk+2151/3696] __link_path_walk+0x867/0xe70
Jun 23 12:25:30 kubuntu kernel: [ 43.565994] [current_fs_time+80/96] current_fs_time+0x50/0x60
Jun 23 12:25:30 kubuntu kernel: [ 43.566069] [link_path_walk+69/192] link_path_walk+0x45/0xc0
Jun 23 12:25:30 kubuntu kernel: [ 43.566160] [do_path_lookup+131/448] do_path_lookup+0x83/0x1c0
Jun 23 12:25:30 kubuntu kernel: [ 43.566191] [__path_lookup_intent_open+81/160] __path_lookup_intent_open+0x51/0xa0
Jun 23 12:25:30 kubuntu kernel: [ 43.566219] [path_lookup_open+32/48] path_lookup_open+0x20/0x30
Jun 23 12:25:30 kubuntu kernel: [ 43.566240] [open_namei+90/1552] open_namei+0x5a/0x610
Jun 23 12:25:30 kubuntu kernel: [ 43.566274] [__handle_mm_fault+1887/2624] __handle_mm_fault+0x75f/0xa40
Jun 23 12:25:30 kubuntu kernel: [ 43.566308] [do_filp_open+51/96] do_filp_open+0x33/0x60
Jun 23 12:25:30 kubuntu kernel: [ 43.566399] [do_sys_open+78/240] do_sys_open+0x4e/0xf0
Jun 23 12:25:30 kubuntu kernel: [ 43.566430] [sys_open+28/32] sys_open+0x1c/0x20
Jun 23 12:25:30 kubuntu kernel: [ 43.566441] [sysenter_past_esp+105/169] sysenter_past_esp+0x69/0xa9
Jun 23 12:25:30 kubuntu kernel: [ 43.566478] [xfrm_state_find+979/1392] xfrm_state_find+0x3d3/0x570
Jun 23 12:25:30 kubuntu kernel: [ 43.566512] =======================
Jun 23 12:25:30 kubuntu kernel: [ 43.566516] Code: 44 24 10 78 20 d5 f8 c7 44 24 0c 80 01 00 00 c7 44 24 08 6d 3d d5 f8 c7 44 24 04 6b 12 d5 f8 c7 04 24 28 1f d5 f8 e8 bf 10 3e c7 <0f> 0b eb fe 89 44 24 0c c7 44 24 08 50 20 d5 f8 c7 44 24 04 6b
Jun 23 12:25:30 kubuntu kernel: [ 43.566681] EIP: [<f8d45b51>] dx_probe+0x1e1/0x320 [ext3] SS:ESP 0068:f6813c74
Jun 23 12:25:37 kubuntu kernel: [ 43.566701] <7>/dev/vmnet: open called by PID 5879 (vmnet-netifup)

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[John Wye (john-wye)]

Hmm, I can't seem to find a way to attach multiple files, so I'll attach them one at a time.

I must warn you, though: my computer is a frequently used dualboot computer, so there have been about three or so reboots since I found the bug. So if you need any earlier version of any log files, just ask.

[John Wye (john-wye)]

I think I'll attach /var/log/kern.log, since I'm not sure dmesg will have given all the relevant info.

You'll find the bug repeated 4 times in kern.log, since I tried rebooting with different kernels etc to see if that was the problem (hadn't thought about actually reading what the bug was ;)).

The first two boots were actually with kernel version 2.6.20-16-generic, the next two with 2.6.20-15-generic.

The bug reports start at lines:
2511
3018
3526
4049

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you. Actually this is a duplicate of bug #109177. Feel free to report any other bug you find.

[Launchpad Janitor (janitor)]

[Expired for linux-source-2.6.20 (Ubuntu) because there has been no activity for 60 days.]