Return-Path: <linux-kernel-owner+willy=40w.ods.org-S1422748AbWJNSab@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1422748AbWJNSab (ORCPT <rfc822;willy@w.ods.org>);
	Sat, 14 Oct 2006 14:30:31 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422747AbWJNSab
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Sat, 14 Oct 2006 14:30:31 -0400
Received: from c-71-197-74-6.hsd1.ca.comcast.net ([71.197.74.6]:29374 "EHLO
	nofear.bounceme.net") by vger.kernel.org with ESMTP
	id S1422748AbWJNSaa (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sat, 14 Oct 2006 14:30:30 -0400
Message-ID: <45312CDC.8090703@syphir.sytes.net>
Date: Sat, 14 Oct 2006 11:30:52 -0700
From: "C.Y.M" <syphir@syphir.sytes.net>
Reply-To: syphir@syphir.sytes.net
Organization: CooLNeT
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
CC: 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
References: <452581D7.5020907@syphir.sytes.net> <4525B546.7070305@yahoo.com.au> <6bffcb0e0610141056t44365ab2p3972d0a95dba33da@mail.gmail.com>
In-Reply-To: <6bffcb0e0610141056t44365ab2p3972d0a95dba33da@mail.gmail.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1572
Lines: 40

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.

Best Regards.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/