Created attachment 394363 [details] Patch that adds the needed flag. Description of problem: The following backtrace was encountered on RHEL5 system with the gfs2 module. crash> log ..... ..... Kernel BUG at ...ir/build/BUILD/gfs2-kmod-1.92/_kmod_build_/trans.c:34 invalid opcode: 0000 [1] SMP last sysfs file: /class/fc_remote_ports/rport-1:0-0/roles CPU 2 Modules linked in: mptctl mptbase ipmi_si(U) ipmi_devintf(U) ipmi_msghandler(U) autofs4 nfs fscache nfs_acl lock_dlm gfs2(U) dlm configfs lockd sunrpc ib_iser libiscsi2 scsi_transport_iscsi2 scsi_transport_iscsi ib_srp rds ib_sdp ib_ipoib ipoib_helper ipv6 xfrm_nalgo crypto_api rdma_ucm rdma_cm ib_ucm ib_uverbs ib_umad ib_cm iw_cm ib_addr ib_sa ib_mad ib_core dm_round_robin dm_multipath scsi_dh video hwmon backlight sbs i2c_ec i2c_core button battery asus_acpi acpi_memhotplug ac parport_pc lp parport e1000e(U) ide_cd pcspkr bnx2(U) serio_raw sg hpilo i5000_edac cdrom edac_mc dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero dm_mirror dm_log dm_mod usb_storage qla2xxx scsi_transport_fc ata_piix libata shpchp cciss sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 17171, comm: cp Tainted: G 2.6.18-164.6.1.el5 #1 RIP: 0010:[<ffffffff8879f2f7>] [<ffffffff8879f2f7>] :gfs2:gfs2_do_trans_begin+0x2c/0x144 RSP: 0018:ffff8100683a1968 EFLAGS: 00010286 RAX: ffff8102854d9040 RBX: 0000000000000005 RCX: 0000000000000001 RDX: 0000000000000001 RSI: 0000000000000005 RDI: ffff81030bcc5000 RBP: ffff81031f05cd50 R08: ffff81000001f600 R09: 000000000000003a R10: ffff8102854d9040 R11: 0000000000000246 R12: 0000000000000001 R13: 0000000000000000 R14: ffff81030bcc5000 R15: 0000000000000001 FS: 00002b1783703f90(0000) GS:ffff81032ff26e40(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00000000004c84f8 CR3: 0000000020d3c000 CR4: 00000000000006e0 Process cp (pid: 17171, threadinfo ffff8100683a0000, task ffff8102854d9040) Stack: ffff8102f0562810 ffff810143cd9cc8 ffff81031f05cd50 ffff8102ee9aeaa8 0000000000000000 ffff81030bcc5000 ffff81031f05cc00 ffffffff8878c95d ffff8100683a19b8 0000000000000000 ffff810143cd9cc8 0000000000000000 Call Trace: [<ffffffff8878c95d>] :gfs2:gfs2_dinode_dealloc+0x123/0x1a7 [<ffffffff88797a17>] :gfs2:gfs2_delete_inode+0xf1/0x18d [<ffffffff8879796c>] :gfs2:gfs2_delete_inode+0x46/0x18d [<ffffffff88797926>] :gfs2:gfs2_delete_inode+0x0/0x18d [<ffffffff8002f48f>] generic_delete_inode+0xc6/0x143 [<ffffffff800ea19d>] prune_one_dentry+0x4d/0x76 [<ffffffff8002e949>] prune_dcache+0x10f/0x149 [<ffffffff800ea1dd>] shrink_dcache_memory+0x17/0x30 [<ffffffff8003f3b6>] shrink_slab+0xdc/0x153 [<ffffffff800ca905>] try_to_free_pages+0x1da/0x2d7 [<ffffffff8000f40d>] __alloc_pages+0x1cb/0x2ce [<ffffffff800c4b08>] grab_cache_page_write_begin+0x4a/0x89 [<ffffffff8000fe54>] generic_file_buffered_write+0x2de/0x675 [<ffffffff8000d174>] file_read_actor+0xbe/0x159 [<ffffffff80016513>] __generic_file_aio_write_nolock+0x369/0x3b6 [<ffffffff800c527f>] __generic_file_write_nolock+0x8f/0xa8 [<ffffffff8009fc08>] autoremove_wake_function+0x0/0x2e [<ffffffff8009fc08>] autoremove_wake_function+0x0/0x2e [<ffffffff80063ad5>] mutex_lock+0xd/0x1d [<ffffffff80062486>] __sched_text_start+0xf6/0xbd6 [<ffffffff800455de>] generic_file_write+0x49/0xa7 [<ffffffff8001691b>] vfs_write+0xce/0x174 [<ffffffff800171d3>] sys_write+0x45/0x6e [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Code: 0f 0b 68 d5 45 7a 88 c2 22 00 44 89 e0 09 d8 75 0a 0f 0b 68 RIP [<ffffffff8879f2f7>] :gfs2:gfs2_do_trans_begin+0x2c/0x144 RSP <ffff8100683a1968> Version-Release number of selected component (if applicable): kernel-2.6.18-164.6.1.el5 How reproducible: Random Steps to Reproduce: 1. Unknown Actual results: Kernel Bug is thrown Expected results: No kernel Bug is thrown Additional info: Spoke with steve whitehouse about this issue and we found out where the problem. Another BZ had similar backtrace. The backtraces were different we found out that a flag was not set in another function leading to a different way to create the bug. https://bugzilla.redhat.com/show_bug.cgi?id=460218#c7 Patch will be upload that resolves the issue.
I wondered why I'd not seen this bug.... so I've already created one of my own and posted the patch. *** This bug has been marked as a duplicate of bug 566221 ***