Hi,
I've been getting these warnings in syslog since I've been running (Linux) kernels 2.6.31.x and up (I'm currently at 2.6.32.2), they do not show up on 2.6.30.x kernels.
Dovecot versions involved were/are 1.2.x, I'm currently at 1.2.9. My system is running Slackware 13.0, but this also happened with 12.2.
------------[ cut here ]------------ WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x2a/0x4b() Hardware name: To Be Filled By O.E.M. inotify closing but id=0 for entry=f61e3334 in group=f254ce00 still in idr. Probably leaking memory Modules linked in: tcp_diag inet_diag autofs4 nfsd lockd nfs_acl sunrpc exportfs ipv6 w83627hf hwmon_vid hwmon lp fuse parport_pc 8250_pnp rtc_cmos 8250 parport rtc_core serial_core rtc_lib ohci_hcd button thermal processor evdev e1000 psmouse serio_raw i2c_i801 ide_cd_mod sg i2c_core cdrom ehci_hcd Pid: 10837, comm: imap Not tainted 2.6.32.2 #1 Call Trace: [<c1024368>] ? warn_slowpath_common+0x5e/0x8a [<c10243c6>] ? warn_slowpath_fmt+0x26/0x2a [<c10953a0>] ? idr_callback+0x2a/0x4b [<c10ed1c5>] ? idr_for_each+0x5a/0x91 [<c1095376>] ? idr_callback+0x0/0x4b [<c1095367>] ? inotify_free_group_priv+0x12/0x21 [<c1093c81>] ? fsnotify_final_destroy_group+0x16/0x1e [<c10954dc>] ? inotify_release+0x16/0x22 [<c1072f76>] ? __fput+0xc0/0x163 [<c1070a90>] ? filp_close+0x4e/0x54 [<c1070afc>] ? sys_close+0x66/0x9c [<c10028b5>] ? syscall_call+0x7/0xb ---[ end trace a2df6cbeb716721c ]--- entry->group=(null) inode=(null) wd=1024
There are no processes other than dovecot's "imap" that are ever causing these warnings. Does this indicate a problem in the kernel or rather in dovecot?
The system appears to run fine except for the warnings, no actual crashes, asserts, core dumps or similar in any of dovecot's components.
Mandatory 'dovecot -n' output:
[root@airframe]:~# dovecot -n
1.2.9: /usr/local/etc/dovecot.conf
OS: Linux 2.6.32.2 i686 Slackware 13.0.0.0.0
login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_max_userip_connections: 20 verbose_proctitle: yes mail_location: maildir:~/Maildir:INBOX=~/Maildir/.INBOX fsync_disable: yes mail_process_size: 2048 mail_plugins: expire fts fts_squat auth default: mechanisms: plain digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/etc/dovecot-passwd userdb: driver: passwd socket: type: listen master: path: /usr/local/var/run/dovecot/auth-master mode: 384 plugin: expire: Trash 7 Junk 1 expire_dict: proxy::expire fts: squat fts_squat: partial=4 full=6 dict: expire: mysql:/usr/local/etc/dovecot-dict-sql-expire.conf [root@airframe]:~#
Thanks & A Happy 2010, Thomas
- Timo Sirainen, 2010-01-02 17:48
Hehe ... okay, so which one is it? :-) I don't even know what exactly to make of this warning - obviously, there may be a potential memory leak related to inotify and dovecot's imap process, but is it
a bug in the kernel that is triggered by something that dovecot's inotify code does, or
a bug in dovecot's imap that the kernel notices and warns about as of 2.6.31 (but didn't notice and/or warn about in 2.6.30 and earlier)?
Hmmm ... I don't mind the warning as such, as it doesn't have any actual bad side effects as far as I can tell, I'm just curious as to what causes it.
Is there anything related I should/could tune in /proc/sys/fs/inotify?
[root@airframe]:~# grep -r . /proc/sys/fs/inotify /proc/sys/fs/inotify/max_user_instances:128 /proc/sys/fs/inotify/max_user_watches:65536 /proc/sys/fs/inotify/max_queued_events:16384 [root@airframe]:~#
Bye, Thomas
On 3.1.2010, at 9.12, Thomas Zajic wrote:
Yes.
Userspace can't (shouldn't) cause kernel errors/warnings. Even if Dovecot did something wrong, I think it would still be a kernel bug if it logged a warning about it. And this doesn't seem to be a widespread problem, so I don't think Dovecot does anything wrong.
Is there anything related I should/could tune in /proc/sys/fs/inotify?
Probably not. I'd ask about this in your distro or kernel mailing list.
participants (3)
-
Noel Butler
-
Thomas Zajic
-
Timo Sirainen