From: "C.Y.M" <syphir@syphir.sytes.net>
To: Nick Piggin <nickpiggin@yahoo.com.au>, linux-kernel@vger.kernel.org
Subject: Re: BUG: warning at fs/inotify.c:181 with linux-2.6.18
Date: Thu, 05 Oct 2006 19:20:17 -0700 [thread overview]
Message-ID: <4525BD61.80400@syphir.sytes.net> (raw)
In-Reply-To: <4525B546.7070305@yahoo.com.au>
Nick Piggin wrote:
> C.Y.M wrote:
>> Since I updated to 2.6.18, I have had the following warnings in my
>> syslog. Is
>> this a known problem? Better yet, is there a solution to this? I am
>> running on
>> a i686 (Athlon XP) 32 bit cpu compiled under gcc-3.4.6.
>>
>>
>> Oct 5 08:27:31 sid kernel: BUG: warning at
>> fs/inotify.c:181/set_dentry_child_flags()
>> Oct 5 08:27:31 sid kernel: [<c0182a10>]
>> set_dentry_child_flags+0x170/0x190
>> Oct 5 08:27:31 sid kernel: [<c0182adf>] remove_watch_no_event+0x5f/0x70
>> Oct 5 08:27:31 sid kernel: [<c0182b08>]
>> inotify_remove_watch_locked+0x18/0x50
>> Oct 5 08:27:31 sid kernel: [<c01833dc>] inotify_rm_wd+0x6c/0xb0
>> Oct 5 08:27:31 sid kernel: [<c0183e98>] sys_inotify_rm_watch+0x38/0x60
>> Oct 5 08:27:31 sid kernel: [<c0102d8f>] syscall_call+0x7/0xb
>
> I don't think it is a known problem. Is it reproduceable? Any idea what
> is making the inotify syscalls?
>
The warning messages start about an hour or two after I boot into the 2.6.18
kernel. I am not doing anything on the machine when it happens. I don't see
any new processes starting up at that time either. As soon as I boot back to
2.6.17.13, there are no more problems. Also, the machine is not running X when
it occurs.
root@sid:~$ grep BUG /var/log/syslog
Oct 5 08:27:31 sid kernel: BUG: warning at
fs/inotify.c:181/set_dentry_child_flags()
Oct 5 11:46:36 sid kernel: BUG: warning at
fs/inotify.c:181/set_dentry_child_flags()
Oct 5 13:24:50 sid kernel: BUG: warning at
fs/inotify.c:181/set_dentry_child_flags()
Oct 5 15:17:55 sid kernel: BUG: warning at
fs/inotify.c:181/set_dentry_child_flags()
Oct 5 16:40:10 sid kernel: BUG: warning at
fs/inotify.c:181/set_dentry_child_flags()
Best Regards.
next prev parent reply other threads:[~2006-10-06 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 22:06 BUG: warning at fs/inotify.c:181 with linux-2.6.18 C.Y.M
2006-10-06 1:45 ` Nick Piggin
2006-10-06 2:20 ` C.Y.M [this message]
2006-10-14 17:40 ` C.Y.M
2006-10-14 17:56 ` Michal Piotrowski
2006-10-14 18:30 ` C.Y.M
2006-10-15 7:49 ` Nick Piggin
2006-11-18 9:21 ` C.Y.M
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=4525BD61.80400@syphir.sytes.net \
--to=syphir@syphir.sytes.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.