From: Eric Paris <eparis@redhat.com>
To: Frantisek Hanzlik <franta@hanzlici.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS in inotify code, kernel 2.6.31.6-162.fc12.i686.PAE
Date: Sun, 20 Dec 2009 19:28:47 -0500 [thread overview]
Message-ID: <1261355327.2782.0.camel@localhost> (raw)
In-Reply-To: <4B2E7841.6020203@hanzlici.cz>
On Sun, 2009-12-20 at 20:17 +0100, Frantisek Hanzlik wrote:
> Frantisek Hanzlik wrote:
> > Hello, when I tried incrond inotify daemon, I found this in system log:
> >
> > Dec 20 05:20:03 franta kernel: ------------[ cut here ]------------
> > Dec 20 05:20:03 franta kernel: WARNING: at
> > fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x32/0x56() (Not
> > tainted)
> > Dec 20 05:20:03 franta kernel: Hardware name: P5E-VM HDMI
> > Dec 20 05:20:03 franta kernel: inotify closing but id=0 for
> > entry=ed0b8900 in group=d657d600 still in idr. Probably leaking memory
> > Dec 20 05:20:03 franta kernel: Modules linked in: bluetooth rfkill hfs
> > hfsplus nls_utf8 fuse ipt_MASQUERADE iptable_nat nf_nat nfsd exportfs
> > autofs4 nfs lock
> > d fscache nfs_acl auth_rpcgss sunrpc bridge stp llc cpufreq_ondemand
> > acpi_cpufreq dm_multipath kvm_intel kvm uinput snd_hda_codec_intelhdmi
> > snd_hda_codec_rea
> > ltek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device
> > snd_pcm snd_timer firewire_ohci snd firewire_core crc_itu_t iTCO_wdt
> > soundcore iTCO_vendor_
> > support asus_atk0110 i2c_i801 snd_page_alloc atl1 serio_raw e100 mii
> > ata_generic pata_acpi pata_jmicron i915 drm_kms_helper drm i2c_algo_bit
> > i2c_core video o
> > utput [last unloaded: microcode]
> > Dec 20 05:20:03 franta kernel: Pid: 7426, comm: incrond Not tainted
> > 2.6.31.6-162.fc12.i686.PAE #1
> > Dec 20 05:20:03 franta kernel: Call Trace:
> > Dec 20 05:20:03 franta kernel: [<c043db1b>] warn_slowpath_common+0x70/0x87
> > Dec 20 05:20:03 franta kernel: [<c04edbfc>] ? idr_callback+0x32/0x56
> > Dec 20 05:20:03 franta kernel: [<c043db70>] warn_slowpath_fmt+0x29/0x2c
> > Dec 20 05:20:03 franta kernel: [<c04edbfc>] idr_callback+0x32/0x56
> > Dec 20 05:20:03 franta kernel: [<c059ce18>] idr_for_each+0x5c/0x97
> > Dec 20 05:20:03 franta kernel: [<c04edbca>] ? idr_callback+0x0/0x56
> > Dec 20 05:20:03 franta kernel: [<c04ec2b0>] ? fsnotify_put_event+0x48/0x4b
> > Dec 20 05:20:03 franta kernel: [<c04edbb9>]
> > inotify_free_group_priv+0x1a/0x2b
> > Dec 20 05:20:03 franta kernel: [<c04ec38f>]
> > fsnotify_final_destroy_group+0x1e/0x28
> > Dec 20 05:20:03 franta kernel: [<c04ec453>] fsnotify_put_group+0x75/0x78
> > Dec 20 05:20:03 franta kernel: [<c04edd71>] inotify_release+0x1e/0x28
> > Dec 20 05:20:03 franta kernel: [<c04c9bd7>] __fput+0xed/0x184
> > Dec 20 05:20:03 franta kernel: [<c04c9c86>] fput+0x18/0x1a
> > Dec 20 05:20:03 franta kernel: [<c04c7129>] filp_close+0x56/0x60
> > Dec 20 05:20:03 franta kernel: [<c043f480>] put_files_struct+0x5d/0xa1
> > Dec 20 05:20:03 franta kernel: [<c043f4f7>] exit_files+0x33/0x37
> > Dec 20 05:20:03 franta kernel: [<c0440c60>] do_exit+0x1cb/0x5da
> > Dec 20 05:20:03 franta kernel: [<c04410d5>] do_group_exit+0x66/0x8d
> > Dec 20 05:20:03 franta kernel: [<c0441114>] sys_exit_group+0x18/0x1c
> > Dec 20 05:20:03 franta kernel: [<c0408f9b>] sysenter_do_call+0x12/0x28
> > Dec 20 05:20:03 franta kernel: ---[ end trace bf2ba6f50ae90f71 ]---
> > Dec 20 05:20:03 franta kernel: entry->group=(null) inode=(null) wd=1024
> > Dec 20 05:20:08 franta abrt: Kerneloops: Reported 1 kernel oopses to Abrt
> > Dec 20 05:20:08 franta abrtd: Directory 'kerneloops-1261282808-1'
> > creation detected
> > Dec 20 05:20:08 franta abrtd: Getting local universal unique identification
> > Dec 20 05:20:08 franta abrtd: New crash, saving
> > Dec 20 05:20:08 franta abrtd: Activation of plugin 'RunApp' was not
> > successful: Plugin 'RunApp' is not registered
> >
> >
> > In addition to things above: System is Fedora 12 i686 linux, Core2 Duo
> > E8200, 4GB RAM,
> > ext4 fs on root (where I had inotify paths - they was somewhere under
> > /home/).
> >
> > Or report to Fedora's bugzilla is more appropriate?
> >
> > Thanks, Franta Hanzlik
>
> Sorry for noise, as I just see this bug is probably already reported by Tim Blechmann's
> mail "WARNING: at fs/notify/inotify/inotify_fsnotify.c:129" from 10 Dec 2009 21:39:00
> and hope solving by Eric Paris.
I did manage to get it set up and reproduced today. I'll work on
debugging it tomorrow. Races are always so fun to find....
-Eric
prev parent reply other threads:[~2009-12-21 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-20 12:57 OOPS in inotify code, kernel 2.6.31.6-162.fc12.i686.PAE Frantisek Hanzlik
2009-12-20 19:17 ` Frantisek Hanzlik
2009-12-21 0:28 ` Eric Paris [this message]
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=1261355327.2782.0.camel@localhost \
--to=eparis@redhat.com \
--cc=franta@hanzlici.cz \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.