Bug#679830: linux-image-2.6.32-5-686: Kernel bug observed in syslog when performing an rsync operation.
Package: linux-2.6
Version: 2.6.32-45
Severity: normal
Kernel bug observed in syslog when performing an rsync operation. I use rsnapshot and I believe an rsnapshot operation "conflicted" or "interfered" somehow with my manual rsync command. The source and destination are USB HDDs with ext4 filesystems. After the kernel bug was observed I discovered the source filesystem had a corrupt filesystem. If it is relevant I was using the rsync command with --hard-links and I also observed messages of this sort: "[1075483.039915] EXT4-fs error (device sdb1): htree_dirblock_to_tree: bad entry in directory #7143723: directory entry across blocks - block=34323866offset=0(0), inode=135151872, rec_len=66180, name_len=66" and "Jul 1 06:33:06 altair kernel: [1075335.376996] EXT4-fs error (device sdb1): ext4_lookup: deleted inode referenced: 8954048".
-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-45) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 04:01:19 UTC 2012
00:1f.4 USB Controller [0c03]: Intel Corporation 82801BA/BAM USB Controller #1 [8086:2444] (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation Device [8086:2411]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 23
Region 4: I/O ports at 2440 [size=32]
Kernel driver in use: uhci_hcd
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801BA/BAM AC'97 Audio Controller [8086:2445] (rev 02)
Subsystem: Compaq Computer Corporation Device [0e11:000f]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 17
Region 0: I/O ports at 2000 [size=256]
Region 1: I/O ports at 2400 [size=64]
Kernel driver in use: Intel ICH
02:04.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at 1000 [size=256]
Region 1: Memory at 40100000 (32-bit, non-prefetchable) [size=256]
[virtual] Expansion ROM at 20000000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: r8169
02:08.0 Ethernet controller [0200]: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller [8086:2449] (rev 01)
Subsystem: Compaq Computer Corporation EtherExpress PRO/100 VM [0e11:0012]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 66 (2000ns min, 14000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 20
Region 0: Memory at 40000000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at 1400 [size=64]
Capabilities: <access denied>
Kernel driver in use: e100
02:09.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 62) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 66, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 18
Region 4: I/O ports at 1440 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
02:09.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 62) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 66, Cache Line Size: 32 bytes
Interrupt: pin B routed to IRQ 21
Region 4: I/O ports at 1460 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
02:09.2 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 65) (prog-if 20 [EHCI])
Subsystem: VIA Technologies, Inc. USB 2.0 [1106:3104]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 66, Cache Line Size: 32 bytes
Interrupt: pin C routed to IRQ 22
Region 0: Memory at 40200000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
** USB devices:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 1058:1003 Western Digital Technologies, Inc.
Bus 002 Device 003: ID 1058:1021 Western Digital Technologies, Inc. Elements 2TB
Bus 002 Device 002: ID 13fd:1340 Initio Corporation Hi-Speed USB to SATA Bridge
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.32-5-686 depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii initramfs-tools [linux-initra 0.98.8 tools for generating an initramfs
ii linux-base 2.6.32-45 Linux image base package
ii module-init-tools 3.12-2+b1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-5-686 recommends:
ii firmware-linux-free 2.6.32-45 Binary firmware for various driver
ii libc6-i686 2.11.3-3 Embedded GNU C Library: Shared lib
Versions of packages linux-image-2.6.32-5-686 suggests:
ii grub 0.97-64 GRand Unified Bootloader (dummy pa
pn linux-doc-2.6.32 <none> (no description available)
Versions of packages linux-image-2.6.32-5-686 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
ii firmware-linux 0.28+squeeze1 Binary firmware for various driver
ii firmware-linux-nonfree 0.28+squeeze1 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
pn xen-hypervisor <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120701221420.1784.81013.reportbug@altair.ejectdi sc.net">http://lists.debian.org/20120701221420.1784.81013.reportbug@altair.ejectdi sc.net
07-22-2012, 04:49 AM
Ben Hutchings
Bug#679830: linux-image-2.6.32-5-686: Kernel bug observed in syslog when performing an rsync operation.
On Sun, 2012-07-01 at 23:14 +0100, Imran Chaudhry wrote:
> Package: linux-2.6
> Version: 2.6.32-45
> Severity: normal
>
> Kernel bug observed in syslog when performing an rsync operation. I
> use rsnapshot and I believe an rsnapshot operation "conflicted" or
> "interfered" somehow with my manual rsync command. The source and
> destination are USB HDDs with ext4 filesystems. After the kernel bug
> was observed I discovered the source filesystem had a corrupt
> filesystem. If it is relevant I was using the rsync command with
> --hard-links and I also observed messages of this sort:
> "[1075483.039915] EXT4-fs error (device sdb1): htree_dirblock_to_tree:
> bad entry in directory #7143723: directory entry across blocks -
> block=34323866offset=0(0), inode=135151872, rec_len=66180,
> name_len=66" and "Jul 1 06:33:06 altair kernel: [1075335.376996]
> EXT4-fs error (device sdb1): ext4_lookup: deleted inode referenced:
> 8954048".
Sorry to hear this. I cannot recommend using ext4 in Linux 2.6.32.
This specific failure mode seems to have been made possible by:
commit 731eb1a03a8445cde2cb23ecfb3580c6fa7bb690
Author: Akinobu Mita <akinobu.mita@gmail.com>
Date: Wed Mar 3 23:55:01 2010 -0500
ext4: consolidate in_range() definitions
which was backported into a stable update. If the 'first' and 'len'
arguments to in_range() are both 0 and either of them is unsigned, it
wrongly returns true. This means that:
may pass ee_len == 0 to ext4_ext_put_in_cache(), triggering the BUG_ON
there. Maybe that's just not a valid case so this doesn't matter, but
it seems like it might be possible with a corrupt filesystem?
Anyway, I think the proper definition of in_range() is:
--
Ben Hutchings
73.46% of all statistics are made up.
07-22-2012, 08:21 AM
Akinobu Mita
Bug#679830: linux-image-2.6.32-5-686: Kernel bug observed in syslog when performing an rsync operation.
2012/7/22 Ben Hutchings <ben@decadent.org.uk>:
> On Sun, 2012-07-01 at 23:14 +0100, Imran Chaudhry wrote:
>> Package: linux-2.6
>> Version: 2.6.32-45
>> Severity: normal
>>
>> Kernel bug observed in syslog when performing an rsync operation. I
>> use rsnapshot and I believe an rsnapshot operation "conflicted" or
>> "interfered" somehow with my manual rsync command. The source and
>> destination are USB HDDs with ext4 filesystems. After the kernel bug
>> was observed I discovered the source filesystem had a corrupt
>> filesystem. If it is relevant I was using the rsync command with
>> --hard-links and I also observed messages of this sort:
>> "[1075483.039915] EXT4-fs error (device sdb1): htree_dirblock_to_tree:
>> bad entry in directory #7143723: directory entry across blocks -
>> block=34323866offset=0(0), inode=135151872, rec_len=66180,
>> name_len=66" and "Jul 1 06:33:06 altair kernel: [1075335.376996]
>> EXT4-fs error (device sdb1): ext4_lookup: deleted inode referenced:
>> 8954048".
>
> Sorry to hear this. I cannot recommend using ext4 in Linux 2.6.32.
>
>> Relevant kernel log trace with bug:
>> Jul 1 05:37:53 altair kernel: [1072022.349172] ------------[ cut here ]------------
>> Jul 1 05:37:53 altair kernel: [1072022.352027] kernel BUG at /build/buildd-linux-2.6_2.6.32-45-i386-yQfQSv/linux-2.6-2.6.32/debian/build/source_i386_none/fs/ext4/extents.c:1873!
>> Jul 1 05:37:53 altair kernel: [1072022.352027] invalid opcode: 0000 [#1] SMP
>> Jul 1 05:37:53 altair kernel: [1072022.352027] last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:02:09.1/usb4/4-0:1.0/bInterfaceProtocol
>> Jul 1 05:37:53 altair kernel: [1072022.352027] Modules linked in: xt_multiport iptable_filter ip_tables x_tables fuse nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ext4 jbd2 crc16 loop raid1 md_mod snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm i2c_i801 snd_timer shpchp snd psmouse evdev soundcore parport_pc parport serio_raw i2c_core snd_page_alloc pcspkr pci_hotplug rng_core processor button ext3 jbd mbcache usb_storage sd_mod crc_t10dif ata_generic ata_piix uhci_hcd e100 libata ehci_hcd thermal floppy r8169 mii usbcore nls_base scsi_mod thermal_sys [last unloaded: scsi_wait_scan]
>> Jul 1 05:37:53 altair kernel: [1072022.352027]
>> Jul 1 05:37:53 altair kernel: [1072022.352027] Pid: 31553, comm: rsync Not tainted (2.6.32-5-686 #1) Deskpro
>> Jul 1 05:37:53 altair kernel: [1072022.352027] EIP: 0060:[<e0ea5b00>] EFLAGS: 00010246 CPU: 0
>> Jul 1 05:37:53 altair kernel: [1072022.352027] EIP is at ext4_ext_get_blocks+0x286/0x1916 [ext4]
>> Jul 1 05:37:53 altair kernel: [1072022.352027] EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000
>> Jul 1 05:37:53 altair kernel: [1072022.352027] ESI: 00000000 EDI: db1216f4 EBP: 00000000 ESP: dfad7ad0
> [...]
>
> This specific failure mode seems to have been made possible by:
>
> commit 731eb1a03a8445cde2cb23ecfb3580c6fa7bb690
> Author: Akinobu Mita <akinobu.mita@gmail.com>
> Date: Wed Mar 3 23:55:01 2010 -0500
>
> ext4: consolidate in_range() definitions
>
> which was backported into a stable update. If the 'first' and 'len'
> arguments to in_range() are both 0 and either of them is unsigned, it
> wrongly returns true. This means that:
>
> if (in_range(iblock, ee_block, ee_len)) {
> ...
> ext4_ext_put_in_cache(inode, ee_block,
> ee_len, ee_start,
> EXT4_EXT_CACHE_EXTENT);
>
> may pass ee_len == 0 to ext4_ext_put_in_cache(), triggering the BUG_ON
> there. Maybe that's just not a valid case so this doesn't matter, but
> it seems like it might be possible with a corrupt filesystem?
>
> Anyway, I think the proper definition of in_range() is:
>
> #define in_range(b, first, len) ((b) >= (first) && ((b) - (first)) < (len))
I agree with this change and it actually resolves the issue:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3015
while my original patch doesn't.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAC5umyikLFP6j-9hjSV814h4tcOUyBr2FFK5LWx2rvYFAEuA@mail.gmail.com
07-22-2012, 10:26 AM
Imran Chaudhry
Bug#679830: linux-image-2.6.32-5-686: Kernel bug observed in syslog when performing an rsync operation.
Sorry to hear this. *I cannot recommend using ext4 in Linux 2.6.32.
Thanks for your reply Ben.
As an aside, from what kernel version would you recommend use of ext4 in?
Maybe I should use (tried and rusted) ext3 for my backup devices. I mentioned this problem in my local LUG and a couple of people reported similar problems with ext4.
“Live as if you were to die tomorrow. Learn as if you were to live forever.” - Indian political and spiritual leader Mahatma Gandhi (1869-1948)
07-22-2012, 01:24 PM
Ben Hutchings
Bug#679830: linux-image-2.6.32-5-686: Kernel bug observed in syslog when performing an rsync operation.
On Sun, 2012-07-22 at 11:26 +0100, Imran Chaudhry wrote:
> Sorry to hear this. I cannot recommend using ext4 in Linux
> 2.6.32.
>
>
> Thanks for your reply Ben.
>
>
> As an aside, from what kernel version would you recommend use of ext4
> in?
I don't know what the minimum would be but I believe it's fine in Linux
3.2, which will be in the next Debian stable release (and is now
available in testing, unstable and squeeze-backports).
> Maybe I should use (tried and rusted) ext3 for my backup devices. I
> mentioned this problem in my local LUG and a couple of people reported
> similar problems with ext4.
Yes, that's a safer choice.
Ben.
--
Ben Hutchings
73.46% of all statistics are made up.
07-22-2012, 11:33 PM
Theodore Ts'o
Bug#679830: linux-image-2.6.32-5-686: Kernel bug observed in syslog when performing an rsync operation.
On Sun, Jul 22, 2012 at 11:26:18AM +0100, Imran Chaudhry wrote:
>
> Thanks for your reply Ben.
>
> As an aside, from what kernel version would you recommend use of ext4 in?
>
> Maybe I should use (tried and rusted) ext3 for my backup devices. I
> mentioned this problem in my local LUG and a couple of people reported
> similar problems with ext4.
There were a lot of important bug fixes were integrated in the oh,
2.6.35 or 2.6.36. Unfortunately, porting the necessary ext4 patches
to 2.6.32 was very difficult, since some of the patches in question
had prerequisites that involved fairly massive changes to the quota
subsystem.
An enterprise distro such as Red Hat could make the backports work,
but it wasn't easy, and Red Hat by policy doesn't release its broken
out patches, so it's hard for Oracle (and Debian) to profit by the
yeoman work done by Eric Sandeen. (Note, by the way, not his fault;
blame Red Hat management.)
As a result, I would strongly recommend that people use a more modern
3.x kernel.
Since Debian Wheezy will be using a 3.2-based kernel, this problem
will be addressed for the Debian stable users (hopefully!) soon.
Regards,
- Ted
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120722233353.GC9958@thunk.org">http://lists.debian.org/20120722233353.GC9958@thunk.org