linux-kernel - Re: BUG: warning at fs/inotify.c:181 with linux-2.6.18

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 15 Oct 2006 17:49:30 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	syphir@...hir.sytes.net
CC:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: BUG: warning at fs/inotify.c:181 with linux-2.6.18

C.Y.M wrote:
> Michal Piotrowski wrote:
> 
>>On 06/10/06, Nick Piggin <nickpiggin@...oo.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 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/