Description of problem: In dmesg | /var/log/messages: ############ BUG: warning at fs/inotify.c:192/set_dentry_child_flags() (Not tainted) Call Trace: [<ffffffff802e84f9>] set_dentry_child_flags+0x6e/0x14d [<ffffffff802e8610>] remove_watch_no_event+0x38/0x47 [<ffffffff802e8637>] inotify_remove_watch_locked+0x18/0x3b [<ffffffff802e8772>] inotify_rm_wd+0x8d/0xb6 [<ffffffff802e8ce8>] sys_inotify_rm_watch+0x46/0x63 [<ffffffff802602f9>] tracesys+0xab/0xb6 BUG: warning at fs/inotify.c:192/set_dentry_child_flags() (Not tainted) Call Trace: [<ffffffff802e84f9>] set_dentry_child_flags+0x6e/0x14d [<ffffffff802e89e9>] inotify_add_watch+0x95/0xcd [<ffffffff8024e71b>] sys_inotify_add_watch+0x135/0x17f [<ffffffff802e8685>] put_inotify_watch+0x2b/0x4d [<ffffffff802af350>] audit_syscall_entry+0x180/0x1b3 [<ffffffff802602f9>] tracesys+0xab/0xb6 ############ Version-Release number of selected component (if applicable): kernel-xen-2.6.18-164.6.1.el5 Steps to Reproduce: Let the VM run, have a few processes that generate coredumps. It seems to happen randomly (but it happened 34 times in 27 days). Additional info: All filesystems are ext3. Maybe see: https://bugzilla.redhat.com/show_bug.cgi?id=248355 Esp. https://bugzilla.redhat.com/show_bug.cgi?id=248355#c13
Created attachment 376730 [details] sanitized dmesg showing BUGs
Interesting, thanks for the report. This seems like a problem in the inotify/fs layer, so I'm going to move this over to the kernel component. Hopefully someone in the filesystem group will recognize the backtrace and can suggest which patch(es) from upstream helped resolve it. Chris Lalancette
fixed in commit 0d71bd5993b630a989d15adc2562a9ffe41cd26d i will backport this today, will you be able to build a test kernel with the patch to verify it works, or will you need me to build a kernel for you?
Created attachment 376940 [details] patch to fix the problem This is the backported patch. Please test it and verify it fixes your problem. If you do not know how to build a kernel with a test patch just let me know and I will build you one to test. Thanks.
I can build and boot a new kernel, but I have no straightforward way to reproduce the bug. Still, I'll test and report. Thanks!
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
*** This bug has been marked as a duplicate of bug 499019 ***