BUG: at fs/inotify.c:182 set_dentry_child_flags() - second
Hi,
I second Patrick McLean's e-mail from 2007/02/27.
Patrick also said he was using nfsd at that point.
WARNING: at fs/inotify.c:182 set_dentry_child_flags() Pid: 19103, comm: gam_server Tainted: P 2.6.24.3-smp #1 [<c01a2087>] set_dentry_child_flags+0x127/0x160 [<c01a2110>] remove_watch_no_event+0x50/0x60 [<c01a2228>] inotify_remove_watch_locked+0x18/0x50 [<c01a258c>] inotify_rm_wd+0x6c/0xb0 [<c01a2ba8>] sys_inotify_rm_watch+0x38/0x60 [<c0104336>] syscall_call+0x7/0xb =======================
Running Slackware 2.6.24.3-smp stock kernel. However, ntpdate ran 1 minute before this occurred (offset 7.4 seconds). Machine was running rsync to a remote NFS server (common rsync, not using rsync protocol) mounted at the local machine.
Regards,
Cesar
--- quote ---
I have this message in the dmesg on a mail server running on an xfs filesystem. It appears to have happened at some point when nfsd was restarted, but I can't seem to convince it to reproduce.
The machine is running Gentoo's 2.6.20 kernel.
BUG: at fs/inotify.c:182 set_dentry_child_flags() Call Trace: [<ffffffff802b7e2a>] set_dentry_child_flags+0xd4/0x132 [<ffffffff802b7eef>] remove_watch_no_event+0x67/0x76 [<ffffffff802b7f16>] inotify_remove_watch_locked+0x18/0x3b [<ffffffff802b8004>] inotify_rm_wd+0x7e/0xa1 [<ffffffff802b8519>] sys_inotify_rm_watch+0x46/0x62 [<ffffffff80253e6e>] system_call+0x7e/0x83
Hello,
Quoted 14 lines
I second Patrick McLean's e-mail from 2007/02/27.
Patrick also said he was using nfsd at that point.
WARNING: at fs/inotify.c:182 set_dentry_child_flags() Pid: 19103, comm: gam_server Tainted: P 2.6.24.3-smp #1 [<c01a2087>] set_dentry_child_flags+0x127/0x160 [<c01a2110>] remove_watch_no_event+0x50/0x60 [<c01a2228>] inotify_remove_watch_locked+0x18/0x50 [<c01a258c>] inotify_rm_wd+0x6c/0xb0 [<c01a2ba8>] sys_inotify_rm_watch+0x38/0x60 [<c0104336>] syscall_call+0x7/0xb =======================
Quoted 4 lines
Running Slackware 2.6.24.3-smp stock kernel. However, ntpdate ran 1 minute before this occurred (offset 7.4 seconds). Machine was running rsync to a remote NFS server (common rsync, not using rsync protocol) mounted at the local machine.
Here, the check itself has been racy (and producing bogus warnings) and
is already removed in current Linus's tree. Thanks for report.
Honza
Signature · 2 lines
Jan Kara <[email protected]> SuSE CR Labs