[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6bffcb0e0610141056t44365ab2p3972d0a95dba33da@mail.gmail.com>
Date: Sat, 14 Oct 2006 19:56:31 +0200
From: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
To: "Nick Piggin" <nickpiggin@...oo.com.au>
Cc: syphir@...hir.sytes.net, linux-kernel@...r.kernel.org
Subject: Re: BUG: warning at fs/inotify.c:181 with linux-2.6.18
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
> Any idea what
> is making the inotify syscalls?
>
> --
> SUSE Labs, Novell Inc.
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
-
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/
Powered by blists - more mailing lists