From: Cesar Suga <sartre@linuxbr.com>
To: linux-kernel@vger.kernel.org
Subject: BUG: at fs/inotify.c:182 set_dentry_child_flags() - second
Date: Wed, 19 Mar 2008 21:00:53 -0300 [thread overview]
Message-ID: <47E1A935.9030705@linuxbr.com> (raw)
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
next reply other threads:[~2008-03-20 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 0:00 Cesar Suga [this message]
2008-03-25 18:20 ` BUG: at fs/inotify.c:182 set_dentry_child_flags() - second Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E1A935.9030705@linuxbr.com \
--to=sartre@linuxbr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.