Description of problem: While running the kernel tests for 2.6.24.7-75.el5rt the kernel panic'd during the racer test. Version-Release number of selected component (if applicable): 2.6.24.7-75.el5rt How reproducible: This happened on several systems Steps to Reproduce: 1. Install RHEL5.2 x86_64 on groucho.rhts.bos.redhat.com or ibm-crichton-02.rhts.bos.redhat.com 2. Install 2.6.24.7-75.el5rt 3. Reboot into debug kernel 4. Run the /kernel/stress/racer test suite from RHTS Actual results: ------------[ cut here ]------------ kernel BUG at fs/inode.c:262! invalid opcode: 0000 [1] PREEMPT SMP CPU 0 Modules linked in: nfs lockd nfs_acl ipv6 autofs4 hidp rfcomm l2cap bluetooth sunrpc dm_multipath video output sbs sbshc battery ac parport_pc lp parport sg tg3 button i2c_i801 pata_acpi i2c_core ata_generic iTCO_wdt iTCO_vendor_support pcspkr shpchp e752x_edac edac_core dm_snapshot dm_zero dm_mirror dm_mod ata_piix libata mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd Pid: 29203, comm: dd Not tainted 2.6.24.7-76.el5rt #1 RIP: 0010:[<ffffffff810c37cc>] [<ffffffff810c37cc>] clear_inode+0x1b/0x110 RSP: 0018:ffff810067ce3d58 EFLAGS: 00010206 RAX: ffffffff88041556 RBX: ffff810077166b70 RCX: ffff81006c51b970 RDX: 00000000000081a4 RSI: ffff810052cdeb70 RDI: ffff810077166b70 RBP: ffff810067ce3d68 R08: 0000000000000000 R09: ffff810067ce3d98 R10: 0000000000000080 R11: ffff810067ce3bb8 R12: ffff8100599faeb8 R13: 0000000001580865 R14: ffff81006c51b970 R15: ffff81007d43a800 FS: 00002b30c9254090(0000) GS:ffffffff813ef100(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 000000316d098640 CR3: 0000000017c2b000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process dd (pid: 29203, threadinfo ffff810067ce2000, task ffff81007d52c080) Stack: ffff8100599faeb8 ffff810077166b70 ffff810067ce3de8 ffffffff8803625f ffff8100599faeb8 ffff8100599faeb8 ffff81006c5181a4 ffff81007dffb180 ffff810067ce3de8 ffff81007d578000 ffff81004c463df8 0000000000000200 Call Trace: [<ffffffff8803625f>] :ext3:ext3_free_inode+0x10c/0x319 [<ffffffff8803911e>] :ext3:ext3_delete_inode+0xba/0xd8 [<ffffffff88039064>] ? :ext3:ext3_delete_inode+0x0/0xd8 [<ffffffff810c39c8>] generic_delete_inode+0xb8/0x138 [<ffffffff810c3a5f>] generic_drop_inode+0x17/0x16f [<ffffffff810c3088>] iput+0x7c/0x80 [<ffffffff810c0987>] dentry_iput+0xa3/0xbb [<ffffffff810c0a5f>] d_kill+0x41/0x61 [<ffffffff810c0f48>] dput+0x10d/0x11a [<ffffffff810b0e7c>] __fput+0x155/0x179 [<ffffffff810b10ca>] fput+0x14/0x16 [<ffffffff810ae1e3>] filp_close+0x66/0x71 [<ffffffff810af5c8>] sys_close+0x99/0xdc [<ffffffff8100c37e>] traceret+0x0/0x5 Expected results: This should pass Additional info: http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=3869800 http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=3869500
Jeff, It seems the fix for "tmpfs: fix kernel BUG in shmem_delete_inode" was really the one that introduced this bug (and at least one more that we haven't seen in the tests). Check the note at BZ457507#c9: ... please include upstream commit d847471d063663b9f36927d265c66a270c0cfaab to the patch you backported. There's a regression introduced in 14fcc23fdc78e9d32372553ccf21758a9bd56fa1. ... Patch: https://bugzilla.redhat.com/attachment.cgi?id=314678
Patch for BZ457507 queued for -78. Hopefully it will fix this issue too.
I finally managed to get access to groucho.rhts.bos.redhat.com. The 2.6.24.7-75.el5rt kernel was not available any more, and 2.6.24.7-74.el5rtdebug did not boot on this machine. The bug is only verified against 2.6.24.7-81.el5rtdebug. The test has been ran three times. The first one failed with: Oct 3 06:30:23 groucho kernel: BUG: MAX_LOCKDEP_CHAINS too low! Oct 3 06:30:23 groucho kernel: turning off the locking correctness validator. The second and third run passed.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2008-0857.html