Description of problem: Warnings in the kernel log (dmesg): BUG: warning at fs/inotify.c:172/set_dentry_child_flags() (Not tainted) [<c0497a37>] set_dentry_child_flags+0x67/0x13d [<c0497c27>] remove_watch_no_event+0x2f/0x3b [<c0497d15>] inotify_remove_watch_locked+0x12/0x3e [<c0600c17>] mutex_lock+0x1a/0x29 [<c0497fdd>] inotify_rm_wd+0x6d/0x8a [<c04983b1>] sys_inotify_rm_watch+0x38/0x4f [<c0404f70>] syscall_call+0x7/0xb Appears randomly, about every second/third day. Version-Release number of selected component (if applicable): 2.6.21-1.3228.fc7 How reproducible: Wait some hours until it comes up randomly. Actual results: Kernel warning but (as far as I can see) no processes killed, data lost or other "ugly" behavior. Expected results: No warning.
still happens with latest kernel-2.6.22.1-41.fc7: WARNING: at fs/inotify.c:172 set_dentry_child_flags() (Not tainted) [<c049b72f>] set_dentry_child_flags+0x67/0x13d [<c049b91f>] remove_watch_no_event+0x2f/0x3b [<c049ba0d>] inotify_remove_watch_locked+0x12/0x3e [<c060a81b>] mutex_lock+0x1a/0x29 [<c049bcd5>] inotify_rm_wd+0x6d/0x8a [<c049c0a9>] sys_inotify_rm_watch+0x38/0x4f [<c0404f8e>] syscall_call+0x7/0xb [<c0600000>] xfrm_add_sa+0x3e7/0x491 ======================= Although this bug/warning isn't critical, it's still strange...
Being chased upstream too.. http://bugzilla.kernel.org/show_bug.cgi?id=8938 no-one is sure why this is happening.
Possible fix is here: http://bugzilla.kernel.org/attachment.cgi?id=12196&action=view
I think, this is fixed upstream now, changing resolution to UPSTREAM.
Not fixed upstream yet.
still happens on latest FC7 Kernel: kernel-2.6.23.1-21.fc7 WARNING: at fs/inotify.c:172 set_dentry_child_flags() (Not tainted) [<c04a3887>] set_dentry_child_flags+0x67/0x13d [<c04a3a77>] remove_watch_no_event+0x2f/0x3b [<c04a3b65>] inotify_remove_watch_locked+0x12/0x3e [<c061bb2b>] mutex_lock+0x1a/0x29 [<c04a3e2d>] inotify_rm_wd+0x6d/0x8a [<c04a4201>] sys_inotify_rm_watch+0x38/0x4f [<c040518a>] syscall_call+0x7/0xb =======================
Helge, You should add yourself to the kernel bug upstream: http://bugzilla.kernel.org/show_bug.cgi?id=8938 as it would appear the maintainer has had issues getting someone to test a fix.
Thanks Christopher. I'll do.
I'm closing this as a dupe of bug #287411 as that has more information and as such is policy for duplicate bugs. Thanks for adding yourself to the upstream bug and for filing this one originally - it is greatly appreciated. *** This bug has been marked as a duplicate of 287411 ***
(In reply to comment #9) > I'm closing this as a dupe of bug #287411 as that has more information and as > such is policy for duplicate bugs. Thanks for adding yourself to the upstream > bug and for filing this one originally - it is greatly appreciated. > > *** This bug has been marked as a duplicate of 287411 *** This is almost certainly net the same problem as that in 248411. It's a coincidence that the reporter saw that in his logs as well. Please also see 427581.
*** This bug has been marked as a duplicate of 287411 ***
Just saw the problem again with kernel 2.6.23.15-80.fc7. Since upstream think it's fixed with 2.6.24, I'll close this bug. Nevertheless, it's NOT A DUPLICATE of #287411 !!!!
I have this same problem on a system running RHEL5 server x86_64, all patches applied: ---- BUG: warning at fs/inotify.c:192/set_dentry_child_flags() (Not tainted) Call Trace: [<ffffffff800f180f>] set_dentry_child_flags+0x6e/0x14d [<ffffffff800f1926>] remove_watch_no_event+0x38/0x47 [<ffffffff800f194d>] inotify_remove_watch_locked+0x18/0x3b [<ffffffff800f1a88>] inotify_rm_wd+0x8d/0xb6 [<ffffffff800f1ffe>] sys_inotify_rm_watch+0x46/0x63 [<ffffffff8005d116>] system_call+0x7e/0x83 ---- Will there be a kernel-fix for RHEL for this problem anytime soon? Or should I just open a new bug?