* Re: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129
@ 2010-01-08 5:12 George Spelvin
2010-01-12 13:57 ` George Spelvin
2010-01-12 15:21 ` Américo Wang
0 siblings, 2 replies; 5+ messages in thread
From: George Spelvin @ 2010-01-08 5:12 UTC (permalink / raw)
To: linux-kernel; +Cc: linux
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129
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
1 sibling, 0 replies; 5+ messages in thread
From: George Spelvin @ 2010-01-12 13:57 UTC (permalink / raw)
To: linux-kernel; +Cc: linux
> This is after almost 12 days of uptime, so it's not exactly rapidly
> repeatable.
I spoke to soon. It appears to be often (but not always) triggered by
the Debian post-install script for udev. That's a bit of a complex
script, and I haven't figured out where yet.
Interestingly, installing the same package (udev_150-1_i386.deb) on
a 32-bit uniprocessor did not trigger the warning.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129
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
1 sibling, 0 replies; 5+ messages in thread
From: Américo Wang @ 2010-01-12 15:21 UTC (permalink / raw)
To: George Spelvin; +Cc: linux-kernel, Eric Paris
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* WARNING: at fs/notify/inotify/inotify_fsnotify.c:129
@ 2009-12-10 20:39 Tim Blechmann
2009-12-15 4:32 ` Christian Kujau
0 siblings, 1 reply; 5+ messages in thread
From: Tim Blechmann @ 2009-12-10 20:39 UTC (permalink / raw)
To: linux-kernel; +Cc: dieb13
[-- Attachment #1: Type: text/plain, Size: 5481 bytes --]
running 2.6.31.6 or 2.6.32 on a server machine, i see the following
warning in my logs:
Dec 9 00:37:37 es kernel: ------------[ cut here ]------------
Dec 9 00:37:37 es kernel: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x2a/0x4b()
Dec 9 00:37:37 es kernel: Hardware name:
Dec 9 00:37:37 es kernel: inotify closing but id=0 for entry=f4582be0 in group=e9811f40 still in idr. Probably leaking memory
Dec 9 00:37:37 es kernel: Modules linked in: xt_multiport ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables dm_mod coretemp fan i2c_i801 i2c_core uhci_hcd e1000e psmouse intel_agp pcspkr serio_raw ehci_hcd button rtc_cmos evdev processor thermal ata_generic
Dec 9 00:37:37 es kernel: Pid: 10623, comm: imap Tainted: G W 2.6.31.6 #2
Dec 9 00:37:37 es kernel: Call Trace:
Dec 9 00:37:37 es kernel: [<c0229095>] ? warn_slowpath_common+0x5e/0x8a
Dec 9 00:37:37 es kernel: [<c02290f3>] ? warn_slowpath_fmt+0x26/0x2a
Dec 9 00:37:37 es kernel: [<c02be26c>] ? idr_callback+0x2a/0x4b
Dec 9 00:37:37 es kernel: [<c032b219>] ? idr_for_each+0x5a/0x91
Dec 9 00:37:37 es kernel: [<c02be242>] ? idr_callback+0x0/0x4b
Dec 9 00:37:37 es kernel: [<c02bc7cb>] ? fsnotify_remove_notify_event+0x27/0x60
Dec 9 00:37:37 es kernel: [<c02be233>] ? inotify_free_group_priv+0x12/0x21
Dec 9 00:37:37 es kernel: [<c02bcae1>] ? fsnotify_final_destroy_group+0x16/0x1e
Dec 9 00:37:37 es kernel: [<c02be3a8>] ? inotify_release+0x16/0x22
Dec 9 00:37:37 es kernel: [<c029b567>] ? __fput+0xc0/0x16a
Dec 9 00:37:37 es kernel: [<c0298c50>] ? filp_close+0x4e/0x54
Dec 9 00:37:37 es kernel: [<c0298cb0>] ? sys_close+0x5a/0x8d
Dec 9 00:37:37 es kernel: [<c0202844>] ? sysenter_do_call+0x12/0x22
Dec 9 00:37:37 es kernel: ---[ end trace 4eaa2a86a8e2da27 ]---
Dec 9 00:37:37 es kernel: entry->group=(null) inode=(null) wd=1024
Dec 9 00:37:37 es kernel: ------------[ cut here ]------------
Dec 9 00:37:37 es kernel: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x2a/0x4b()
Dec 9 00:37:37 es kernel: Hardware name:
Dec 9 00:37:37 es kernel: inotify closing but id=0 for entry=f54ef3ac in group=f59681c0 still in idr. Probably leaking memory
Dec 9 00:37:37 es kernel: Modules linked in: xt_multiport ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables dm_mod coretemp fan i2c_i801 i2c_core uhci_hcd e1000e psmouse intel_agp pcspkr serio_raw ehci_hcd button rtc_cmos evdev processor thermal ata_generic
Dec 9 00:37:37 es kernel: Pid: 11453, comm: imap Tainted: G W 2.6.31.6 #2
Dec 9 00:37:37 es kernel: Call Trace:
Dec 9 00:37:37 es kernel: [<c0229095>] ? warn_slowpath_common+0x5e/0x8a
Dec 9 00:37:37 es kernel: [<c02290f3>] ? warn_slowpath_fmt+0x26/0x2a
Dec 9 00:37:37 es kernel: [<c02be26c>] ? idr_callback+0x2a/0x4b
Dec 9 00:37:37 es kernel: [<c032b219>] ? idr_for_each+0x5a/0x91
Dec 9 00:37:37 es kernel: [<c02be242>] ? idr_callback+0x0/0x4b
Dec 9 00:37:37 es kernel: [<c02be233>] ? inotify_free_group_priv+0x12/0x21
Dec 9 00:37:37 es kernel: [<c02bcae1>] ? fsnotify_final_destroy_group+0x16/0x1e
Dec 9 00:37:37 es kernel: [<c02be3a8>] ? inotify_release+0x16/0x22
Dec 9 00:37:37 es kernel: [<c029b567>] ? __fput+0xc0/0x16a
Dec 9 00:37:37 es kernel: [<c0298c50>] ? filp_close+0x4e/0x54
Dec 9 00:37:37 es kernel: [<c0298cb0>] ? sys_close+0x5a/0x8d
Dec 9 00:37:37 es kernel: [<c0202844>] ? sysenter_do_call+0x12/0x22
Dec 9 00:37:37 es kernel: ---[ end trace 4eaa2a86a8e2da28 ]---
Dec 9 00:37:37 es kernel: entry->group=(null) inode=(null) wd=1024
Dec 10 00:32:10 es kernel: ------------[ cut here ]------------
Dec 10 00:32:10 es kernel: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x2a/0x4b()
Dec 10 00:32:10 es kernel: Hardware name:
Dec 10 00:32:10 es kernel: inotify closing but id=0 for entry=ee6d47e4 in group=f585fe40 still in idr. Probably leaking memory
Dec 10 00:32:10 es kernel: Modules linked in: xt_multiport ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables dm_mod coretemp fan uhci_hcd i2c_i801 pcspkr psmouse i2c_core serio_raw thermal ehci_hcd intel_agp rtc_cmos evdev e1000e processor ata_generic button
Dec 10 00:32:10 es kernel: Pid: 11428, comm: imap Tainted: G W 2.6.32 #1
Dec 10 00:32:10 es kernel: Call Trace:
Dec 10 00:32:10 es kernel: [<c022af3d>] ? warn_slowpath_common+0x5e/0x8a
Dec 10 00:32:10 es kernel: [<c022af9b>] ? warn_slowpath_fmt+0x26/0x2a
Dec 10 00:32:10 es kernel: [<c02c86c0>] ? idr_callback+0x2a/0x4b
Dec 10 00:32:10 es kernel: [<c0336711>] ? idr_for_each+0x5a/0x91
Dec 10 00:32:10 es kernel: [<c02c8696>] ? idr_callback+0x0/0x4b
Dec 10 00:32:10 es kernel: [<c02c8687>] ? inotify_free_group_priv+0x12/0x21
Dec 10 00:32:10 es kernel: [<c02c6f39>] ? fsnotify_final_destroy_group+0x16/0x1e
Dec 10 00:32:10 es kernel: [<c02c87fc>] ? inotify_release+0x16/0x22
Dec 10 00:32:10 es kernel: [<c02a4e06>] ? __fput+0xc0/0x16a
Dec 10 00:32:10 es kernel: [<c02a24dc>] ? filp_close+0x4e/0x54
Dec 10 00:32:10 es kernel: [<c02a253c>] ? sys_close+0x5a/0x8d
Dec 10 00:32:10 es kernel: [<c0202844>] ? sysenter_do_call+0x12/0x22
Dec 10 00:32:10 es kernel: ---[ end trace 4eaa2a86a8e2da24 ]---
Dec 10 00:32:10 es kernel: entry->group=(null) inode=(null) wd=1024
hth, tim
--
tim@klingt.org
http://tim.klingt.org
Our products just aren't engineered for security.
Brian Valentine, Microsoft's vice president of Windows development
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129
2009-12-10 20:39 Tim Blechmann
@ 2009-12-15 4:32 ` Christian Kujau
0 siblings, 0 replies; 5+ messages in thread
From: Christian Kujau @ 2009-12-15 4:32 UTC (permalink / raw)
To: Tim Blechmann; +Cc: LKML, dieb13, eparis
On Thu, 10 Dec 2009 at 21:39, Tim Blechmann wrote:
> Dec 9 00:37:37 es kernel: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x2a/0x4b()
I've got a similar message here too, with 2.6.32-rc8. However, I'm not
sure how to reproduce this one...
@Eric, should we reopen #14090 or create a new bug?
Thanks,
Christian.
[0] http://bugzilla.kernel.org/show_bug.cgi?id=14090
------------[ cut here ]------------
WARNING: at /data/Scratch/scm/linux-2.6-git/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x36/0x60()
inotify closing but id=0 for entry=ffff88004f8a59a0 in group=ffff880003be0200 still in idr. Probably leaking memory
Modules linked in: sit tunnel4 xfs sha256_generic aes_x86_64 aes_generic nfsd lockd auth_rpcgss sunrpc exportfs ipv6 tun jfs nls_base reiserfs fuse twofish_x86_64 twofish_common
Pid: 9740, comm: imap Not tainted 2.6.32-rc8 #4
Call Trace:
[<ffffffff810ce906>] ? idr_callback+0x36/0x60
[<ffffffff810ce906>] ? idr_callback+0x36/0x60
[<ffffffff810352c9>] ? warn_slowpath_common+0x79/0xd0
[<ffffffff81035381>] ? warn_slowpath_fmt+0x51/0x60
[<ffffffff8120326c>] ? _spin_lock_irq+0xc/0x10
[<ffffffff81200bcf>] ? wait_for_common+0x15f/0x1a0
[<ffffffff8100e4b2>] ? check_events+0x12/0x20
[<ffffffff810cd627>] ? fsnotify_flush_notify+0x97/0xc0
[<ffffffff8100dd99>] ? xen_force_evtchn_callback+0x9/0x10
[<ffffffff8100e4b2>] ? check_events+0x12/0x20
[<ffffffff810ce906>] ? idr_callback+0x36/0x60
[<ffffffff81138d04>] ? idr_for_each+0x84/0xe0
[<ffffffff810ce8d0>] ? idr_callback+0x0/0x60
[<ffffffff8100e49f>] ? xen_restore_fl_direct_end+0x0/0x1
[<ffffffff81096a77>] ? kmem_cache_free+0x87/0xc0
[<ffffffff810ce8ba>] ? inotify_free_group_priv+0x1a/0x30
[<ffffffff810cd6cb>] ? fsnotify_final_destroy_group+0x1b/0x30
[<ffffffff810ceb4c>] ? inotify_release+0x2c/0x50
[<ffffffff8109e450>] ? __fput+0xc0/0x1f0
[<ffffffff8109a9cb>] ? filp_close+0x5b/0x90
[<ffffffff8109aab3>] ? sys_close+0xb3/0x120
[<ffffffff81010d42>] ? system_call_fastpath+0x16/0x1b
---[ end trace 50bb54b8ed08a018 ]---
entry->group=(null) inode=(null) wd=4096
--
BOFH excuse #119:
evil hackers from Serbia.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-01-12 15:19 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
-- strict thread matches above, loose matches on Subject: below --
2009-12-10 20:39 Tim Blechmann
2009-12-15 4:32 ` Christian Kujau
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox