public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: George Spelvin <linux@horizon.com>
Cc: linux-kernel@vger.kernel.org, Eric Paris <eparis@redhat.com>
Subject: Re: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129
Date: Tue, 12 Jan 2010 23:21:03 +0800	[thread overview]
Message-ID: <20100112152103.GE3925@hack> (raw)
In-Reply-To: <20100108051219.3498.qmail@science.horizon.com>

On Fri, Jan 08, 2010 at 12:12:19AM -0500, George Spelvin wrote:
>Like others, I've got this message, but with a more recent kernel:
>2.6.33-rc2.  This is after almost 12 days of uptime, so it's not
>exactly rapidly repeatable.
>
>x86-64 quad-core kernel, 32-bit (Debian/unstable) userland.  8GiB RAM.
>
>------------[ cut here ]------------
>WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x36/0x58()
>Hardware name: MS-7376
>inotify closing but id=0 for entry=ffff880009762a10 in group=ffff880221a4a700 still in idr.  Probably leaking memory
>Pid: 4171, comm: imap Not tainted 2.6.33-rc2 #95
>Call Trace:
> [<ffffffff8102f45a>] ? warn_slowpath_common+0x71/0x87
> [<ffffffff8102f4c2>] ? warn_slowpath_fmt+0x40/0x45
> [<ffffffff8102b6d5>] ? default_wake_function+0x0/0xf
> [<ffffffff810ab03f>] ? idr_callback+0x36/0x58
> [<ffffffff811551d8>] ? idr_for_each+0x64/0xa7
> [<ffffffff8107ed4e>] ? virt_to_head_page+0x9/0x2b
> [<ffffffff810aaff8>] ? inotify_free_group_priv+0x1a/0x2b
> [<ffffffff810a9b2c>] ? fsnotify_final_destroy_group+0x1b/0x24
> [<ffffffff810ab1c9>] ? inotify_release+0x24/0x2f
> [<ffffffff8108610c>] ? __fput+0xef/0x17b
> [<ffffffff8108389d>] ? filp_close+0x54/0x5f
> [<ffffffff81083939>] ? sys_close+0x91/0xc4
> [<ffffffff810233d4>] ? cstar_dispatch+0x7/0x2b
>---[ end trace 5507e3370989315e ]---
>entry->group=(null) inode=(null) wd=4096

inotify is going to be removed, I think.

Adding Eric into Cc...

Anyway, thanks for reporting it!

-- 
Live like a child, think like the god.
 

  parent reply	other threads:[~2010-01-12 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08  5:12 WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 George Spelvin
2010-01-12 13:57 ` George Spelvin
2010-01-12 15:21 ` Américo Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-10 20:39 Tim Blechmann
2009-12-15  4:32 ` Christian Kujau

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=20100112152103.GE3925@hack \
    --to=xiyou.wangcong@gmail.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox