Bug 15023 - Inotify produces errors a bit before the machine goes mad and panics
Summary: Inotify produces errors a bit before the machine goes mad and panics
Status: RESOLVED DUPLICATE of bug 14646
Alias: None
Product: Other
Classification: Unclassified
Component: Modules (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: Eric Paris
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-10 05:22 UTC by Gil Disatnik
Modified: 2010-01-16 14:02 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.31.6
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description Gil Disatnik 2010-01-10 05:22:56 UTC
Hi, this happened twice already, my machine simply hanged and rebooted itself, but I saw these messages before it did, at least once it happened quite a while before it hanged.

Running Debian and a self compiled vanilla 2.6.31.6

kernel: ------------[ cut here ]------------
kernel: WARNING: at fs/notify/inotify/inotify_user.c:398 inotify_remove_from_idr+0x5d/0x9f()
kernel: Hardware name: X7SBi
kernel: Modules linked in: tcp_yeah tcp_vegas coretemp w83627hf w83793 hwmon_vid hwmon loop e1000e i2c_i801 i2c_core ide_pci_generic
kernel: Pid: 1060, comm: udevd Not tainted 2.6.31.6newserv #1
kernel: Call Trace:
kernel: [<ffffffff810a817e>] ? inotify_remove_from_idr+0x5d/0x9f
kernel: [<ffffffff8102ca7f>] warn_slowpath_common+0x77/0xa4
kernel: [<ffffffff8102cabb>] warn_slowpath_null+0xf/0x11
kernel: [<ffffffff810a817e>] inotify_remove_from_idr+0x5d/0x9f
kernel: [<ffffffff810a870d>] inotify_ignored_and_remove_idr+0x8a/0xa5
kernel: [<ffffffff810a7aa9>] inotify_freeing_mark+0x9/0xb
kernel: [<ffffffff810a65aa>] fsnotify_destroy_mark_by_entry+0x124/0x14b
kernel: [<ffffffff810a6762>] fsnotify_clear_marks_by_group+0xb4/0xde
kernel: [<ffffffff810a7cc5>] inotify_release+0x1d/0x37
kernel: [<ffffffff8107f59e>] __fput+0xf6/0x1bb
kernel: [<ffffffff8107f67b>] fput+0x18/0x1a
kernel: [<ffffffff8107c9de>] filp_close+0x67/0x72
kernel: [<ffffffff8102e255>] put_files_struct+0x6b/0xc2
kernel: [<ffffffff8102e2f3>] exit_files+0x47/0x50
kernel: [<ffffffff8102f85f>] do_exit+0x199/0x5ef
kernel: [<ffffffff810412d3>] ? up_read+0x9/0xb
kernel: [<ffffffff8101ce82>] ? do_page_fault+0x1af/0x1de
kernel: [<ffffffff8102fd27>] do_group_exit+0x72/0x9f
kernel: [<ffffffff8102fd66>] sys_exit_group+0x12/0x16
kernel: [<ffffffff8100aeab>] system_call_fastpath+0x16/0x1b
kernel: ---[ end trace b4312697c9ebd4d9 ]---
kernel: ------------[ cut here ]------------
kernel: WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x3e/0x62()
kernel: Hardware name: X7SBi
kernel: inotify closing but id=0 for entry=ffff88022deef540 in group=ffff88022f254100 still in idr.  Probably leaking memory
kernel: Modules linked in: tcp_yeah tcp_vegas coretemp w83627hf w83793 hwmon_vid hwmon loop e1000e i2c_i801 i2c_core ide_pci_generic
kernel: Pid: 1060, comm: udevd Tainted: G        W  2.6.31.6newserv #1
kernel: Call Trace:
kernel: [<ffffffff810a7b1f>] ? idr_callback+0x3e/0x62
kernel: [<ffffffff8102ca7f>] warn_slowpath_common+0x77/0xa4
kernel: [<ffffffff8102cb21>] warn_slowpath_fmt+0x64/0x66
kernel: [<ffffffff81234d78>] ? schedule_timeout+0x24/0x160
kernel: [<ffffffff812342a6>] ? wait_for_common+0xd5/0x130
kernel: [<ffffffff810296f4>] ? default_wake_function+0x0/0xf
kernel: [<ffffffff810a7b1f>] idr_callback+0x3e/0x62
kernel: [<ffffffff810fce9a>] idr_for_each+0x6f/0xb2
kernel: [<ffffffff810a7ae1>] ? idr_callback+0x0/0x62
kernel: [<ffffffff810a5d12>] ? fsnotify_put_event+0x54/0x58
kernel: [<ffffffff810a7acd>] inotify_free_group_priv+0x22/0x36
kernel: [<ffffffff810a5e2f>] fsnotify_final_destroy_group+0x23/0x2f
kernel: [<ffffffff810a5f17>] fsnotify_put_group+0x8f/0x93
kernel: [<ffffffff810a7ccd>] inotify_release+0x25/0x37
kernel: [<ffffffff8107f59e>] __fput+0xf6/0x1bb
kernel: [<ffffffff8107f67b>] fput+0x18/0x1a
kernel: [<ffffffff8107c9de>] filp_close+0x67/0x72
kernel: [<ffffffff8102e255>] put_files_struct+0x6b/0xc2
kernel: [<ffffffff8102e2f3>] exit_files+0x47/0x50
kernel: [<ffffffff8102f85f>] do_exit+0x199/0x5ef
kernel: [<ffffffff810412d3>] ? up_read+0x9/0xb
kernel: [<ffffffff8101ce82>] ? do_page_fault+0x1af/0x1de
kernel: [<ffffffff8102fd27>] do_group_exit+0x72/0x9f
kernel: [<ffffffff8102fd66>] sys_exit_group+0x12/0x16
kernel: [<ffffffff8100aeab>] system_call_fastpath+0x16/0x1b
kernel: ---[ end trace b4312697c9ebd4da ]---

Please tell me if you require any more information,
Thanks
Comment 1 Eric Paris 2010-01-16 14:02:33 UTC

*** This bug has been marked as a duplicate of bug 14646 ***

Note You need to log in before you can comment on or make changes to this bug.