I get very similar error on Hardy with 2.6.24-4 kernel when running kde4:
[29030.741624] WARNING: at /build/buildd/linux-2.6.24/fs/inotify.c:172 set_dentry_child_flags() [29030.741638] Pid: 5928, comm: kded4 Not tainted 2.6.24-3-generic #1 [29030.741664] [<c01b204f>] set_dentry_child_flags+0xcf/0x160 [29030.741693] [<c01b2130>] remove_watch_no_event+0x50/0x60 [29030.741707] [<c01b2248>] inotify_remove_watch_locked+0x18/0x50 [29030.741720] [<c018860e>] vfs_write+0x11e/0x140 [29030.741733] [<c01b25ac>] inotify_rm_wd+0x6c/0xb0 [29030.741750] [<c01b2bc8>] sys_inotify_rm_watch+0x38/0x60 [29030.741764] [<c01053a2>] sysenter_past_esp+0x6b/0xa9 [29030.741786] [<c0300000>] km_new_mapping+0x10/0x70 [29030.741806] ======================= [29030.741939] WARNING: at /build/buildd/linux-2.6.24/fs/inotify.c:172 set_dentry_child_flags() [29030.741946] Pid: 5928, comm: kded4 Not tainted 2.6.24-3-generic #1 [29030.741966] [<c01b204f>] set_dentry_child_flags+0xcf/0x160 [29030.741989] [<c01b28c2>] inotify_add_watch+0xe2/0xf0 [29030.742008] [<c01b3333>] sys_inotify_add_watch+0x153/0x180 [29030.742027] [<c01b2515>] put_inotify_watch+0x35/0x60 [29030.742046] [<c01b2515>] put_inotify_watch+0x35/0x60 [29030.742058] [<c01b25c1>] inotify_rm_wd+0x81/0xb0 [29030.742078] [<c01053a2>] sysenter_past_esp+0x6b/0xa9 [29030.742099] [<c0300000>] km_new_mapping+0x10/0x70 [29030.742117] =======================
Is it possible that this is user-space problem (like kde4 calling system call with wrong options)?
I get very similar error on Hardy with 2.6.24-4 kernel when running kde4:
[29030.741624] WARNING: at /build/ buildd/ linux-2. 6.24/fs/ inotify. c:172 set_dentry_ child_flags( ) child_flags+ 0xcf/0x160 watch_no_ event+0x50/ 0x60 remove_ watch_locked+ 0x18/0x50 0x11e/0x140 rm_wd+0x6c/ 0xb0 rm_watch+ 0x38/0x60 past_esp+ 0x6b/0xa9 mapping+ 0x10/0x70 ======= ======= == buildd/ linux-2. 6.24/fs/ inotify. c:172 set_dentry_ child_flags( ) child_flags+ 0xcf/0x160 add_watch+ 0xe2/0xf0 add_watch+ 0x153/0x180 watch+0x35/ 0x60 watch+0x35/ 0x60 rm_wd+0x81/ 0xb0 past_esp+ 0x6b/0xa9 mapping+ 0x10/0x70 ======= ======= ==
[29030.741638] Pid: 5928, comm: kded4 Not tainted 2.6.24-3-generic #1
[29030.741664] [<c01b204f>] set_dentry_
[29030.741693] [<c01b2130>] remove_
[29030.741707] [<c01b2248>] inotify_
[29030.741720] [<c018860e>] vfs_write+
[29030.741733] [<c01b25ac>] inotify_
[29030.741750] [<c01b2bc8>] sys_inotify_
[29030.741764] [<c01053a2>] sysenter_
[29030.741786] [<c0300000>] km_new_
[29030.741806] =======
[29030.741939] WARNING: at /build/
[29030.741946] Pid: 5928, comm: kded4 Not tainted 2.6.24-3-generic #1
[29030.741966] [<c01b204f>] set_dentry_
[29030.741989] [<c01b28c2>] inotify_
[29030.742008] [<c01b3333>] sys_inotify_
[29030.742027] [<c01b2515>] put_inotify_
[29030.742046] [<c01b2515>] put_inotify_
[29030.742058] [<c01b25c1>] inotify_
[29030.742078] [<c01053a2>] sysenter_
[29030.742099] [<c0300000>] km_new_
[29030.742117] =======
Is it possible that this is user-space problem (like kde4 calling system call with wrong options)?