From: Nick Piggin <nickpiggin@yahoo.com.au>
To: syphir@syphir.sytes.net
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: BUG: warning at fs/inotify.c:181 with linux-2.6.18
Date: Sun, 15 Oct 2006 17:49:30 +1000 [thread overview]
Message-ID: <4531E80A.6@yahoo.com.au> (raw)
In-Reply-To: <45312CDC.8090703@syphir.sytes.net>
C.Y.M wrote:
> Michal Piotrowski wrote:
>
>>On 06/10/06, Nick Piggin <nickpiggin@yahoo.com.au> 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?
>>
>>It is a known problem.
>>http://www.ussg.iu.edu/hypermail/linux/kernel/0608.1/1209.html
>>
>
>
> Thank you for the confirmation. Please include me in this thread if someone
> finds the answer. This bug seems to occur very frequently on my machine with
> 2.6.18.1 so I have been forced to revert back to 2.6.17.13 until I can fix it.
I haven't got around to looking at it yet, sorry.
It does seem like my inotify scalability patch is involved, however it is
interesting that you cannot reproduce the problem in 2.6.17.13.
I probably won't get around to having a look at it for a while, but if you
would like to speed up the process you could try running a git bisect to
find which patch is making the error trigger for you.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-10-15 7:49 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
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 [this message]
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=4531E80A.6@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=syphir@syphir.sytes.net \
/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.