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]

Message-ID: <45312CDC.8090703@syphir.sytes.net>
Date:	Sat, 14 Oct 2006 11:30:52 -0700
From:	"C.Y.M" <syphir@...hir.sytes.net>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
CC:	Nick Piggin <nickpiggin@...oo.com.au>, linux-kernel@...r.kernel.org
Subject: Re: BUG: warning at fs/inotify.c:181 with linux-2.6.18

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.

Best Regards.

-
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/