Skip to contentSkip to conversation

WARNING: at fs/notify/inotify/inotify_fsnotify.c:129

DISCUSSION George Spelvin 2 participants 3 messages Jan 8, 2010 – Jan 12, 2010

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 2 lines

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.

#2 lore raw
In reply to George Spelvin
Quoted 26 lines · George Spelvin

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 ]---
Quoted 1 line

entry->group=(null) inode=(null) wd=4096

inotify is going to be removed, I think.

Adding Eric into Cc...

Anyway, thanks for reporting it!

Signature · 1 line
Live like a child, think like the god.