BUG: warning at fs/inotify.c:181 with linux-2.6.18
Since I updated to 2.6.18, I have had the following warnings in my syslog. Is this a known problem? Better yet, is there a solution to this? I am running on a i686 (Athlon XP) 32 bit cpu compiled under gcc-3.4.6.
Oct 5 08:27:31 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 08:27:31 sid kernel: [<c0182a10>] set_dentry_child_flags+0x170/0x190 Oct 5 08:27:31 sid kernel: [<c0182adf>] remove_watch_no_event+0x5f/0x70 Oct 5 08:27:31 sid kernel: [<c0182b08>] inotify_remove_watch_locked+0x18/0x50 Oct 5 08:27:31 sid kernel: [<c01833dc>] inotify_rm_wd+0x6c/0xb0 Oct 5 08:27:31 sid kernel: [<c0183e98>] sys_inotify_rm_watch+0x38/0x60 Oct 5 08:27:31 sid kernel: [<c0102d8f>] syscall_call+0x7/0xb
Best Regards.
Quoted 5 lines · C.Y.M
Since I updated to 2.6.18, I have had the following warnings in my syslog. Is this a known problem? Better yet, is there a solution to this? I am running on a i686 (Athlon XP) 32 bit cpu compiled under gcc-3.4.6.
Quoted 8 lines
Oct 5 08:27:31 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 08:27:31 sid kernel: [<c0182a10>] set_dentry_child_flags+0x170/0x190 Oct 5 08:27:31 sid kernel: [<c0182adf>] remove_watch_no_event+0x5f/0x70 Oct 5 08:27:31 sid kernel: [<c0182b08>] inotify_remove_watch_locked+0x18/0x50 Oct 5 08:27:31 sid kernel: [<c01833dc>] inotify_rm_wd+0x6c/0xb0 Oct 5 08:27:31 sid kernel: [<c0183e98>] sys_inotify_rm_watch+0x38/0x60 Oct 5 08:27:31 sid kernel: [<c0102d8f>] syscall_call+0x7/0xb
I don't think it is a known problem. Is it reproduceable? Any idea what is making the inotify syscalls?
Signature · 2 lines
SUSE Labs, Novell Inc. Send instant messages to your online friends http://au.messenger.yahoo.com
Quoted 19 lines · Nick Piggin
Quoted 7 lines · C.Y.M
Since I updated to 2.6.18, I have had the following warnings in my syslog. Is
this a known problem? Better yet, is there a solution to this? I am running on
a i686 (Athlon XP) 32 bit cpu compiled under gcc-3.4.6.Quoted 10 lines
Oct 5 08:27:31 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 08:27:31 sid kernel: [<c0182a10>] set_dentry_child_flags+0x170/0x190 Oct 5 08:27:31 sid kernel: [<c0182adf>] remove_watch_no_event+0x5f/0x70 Oct 5 08:27:31 sid kernel: [<c0182b08>] inotify_remove_watch_locked+0x18/0x50 Oct 5 08:27:31 sid kernel: [<c01833dc>] inotify_rm_wd+0x6c/0xb0 Oct 5 08:27:31 sid kernel: [<c0183e98>] sys_inotify_rm_watch+0x38/0x60 Oct 5 08:27:31 sid kernel: [<c0102d8f>] syscall_call+0x7/0xb
Quoted 3 lines
I don't think it is a known problem. Is it reproduceable? Any idea what is making the inotify syscalls?
The warning messages start about an hour or two after I boot into the 2.6.18 kernel. I am not doing anything on the machine when it happens. I don't see any new processes starting up at that time either. As soon as I boot back to 2.6.17.13, there are no more problems. Also, the machine is not running X when it occurs.
root@sid:~$ grep BUG /var/log/syslog Oct 5 08:27:31 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 11:46:36 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 13:24:50 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 15:17:55 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 16:40:10 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags()
Best Regards.
Quoted 29 lines · C.Y.M
Quoted 18 lines · Nick Piggin
Quoted 7 lines · C.Y.M
Since I updated to 2.6.18, I have had the following warnings in my syslog. Is
this a known problem? Better yet, is there a solution to this? I am running on
a i686 (Athlon XP) 32 bit cpu compiled under gcc-3.4.6.Quoted 10 lines
Oct 5 08:27:31 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 08:27:31 sid kernel: [<c0182a10>] set_dentry_child_flags+0x170/0x190 Oct 5 08:27:31 sid kernel: [<c0182adf>] remove_watch_no_event+0x5f/0x70 Oct 5 08:27:31 sid kernel: [<c0182b08>] inotify_remove_watch_locked+0x18/0x50 Oct 5 08:27:31 sid kernel: [<c01833dc>] inotify_rm_wd+0x6c/0xb0 Oct 5 08:27:31 sid kernel: [<c0183e98>] sys_inotify_rm_watch+0x38/0x60 Oct 5 08:27:31 sid kernel: [<c0102d8f>] syscall_call+0x7/0xbQuoted 3 lines
I don't think it is a known problem. Is it reproduceable? Any idea what is making the inotify syscalls?
The warning messages start about an hour or two after I boot into the 2.6.18 kernel. I am not doing anything on the machine when it happens. I don't see any new processes starting up at that time either. As soon as I boot back to 2.6.17.13, there are no more problems. Also, the machine is not running X when it occurs.
Quoted 12 lines
root@sid:~$ grep BUG /var/log/syslog Oct 5 08:27:31 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 11:46:36 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 13:24:50 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 15:17:55 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 16:40:10 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags()
This bug just happened again with 2.6.18.1. Has anyone else noticed this in their logs? I would really like to make that error go away. Any Ideas? I do not see anything that would cause this to happen.
Best Regards.
Quoted 15 lines · Nick Piggin
Quoted 5 lines · C.Y.M
Since I updated to 2.6.18, I have had the following warnings in my syslog. Is this a known problem? Better yet, is there a solution to this? I am running on a i686 (Athlon XP) 32 bit cpu compiled under gcc-3.4.6.
Quoted 8 lines
Oct 5 08:27:31 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 08:27:31 sid kernel: [<c0182a10>] set_dentry_child_flags+0x170/0x190 Oct 5 08:27:31 sid kernel: [<c0182adf>] remove_watch_no_event+0x5f/0x70 Oct 5 08:27:31 sid kernel: [<c0182b08>] inotify_remove_watch_locked+0x18/0x50 Oct 5 08:27:31 sid kernel: [<c01833dc>] inotify_rm_wd+0x6c/0xb0 Oct 5 08:27:31 sid kernel: [<c0183e98>] sys_inotify_rm_watch+0x38/0x60 Oct 5 08:27:31 sid kernel: [<c0102d8f>] syscall_call+0x7/0xb
Quoted 1 line
I don't think it is a known problem. Is it reproduceable?
It is a known problem.
http://www.ussg.iu.edu/hypermail/linux/kernel/0608.1/1209.html
Quoted 5 lines
Any idea what
is making the inotify syscalls?--
SUSE Labs, Novell Inc.
Regards,
Michal
Signature · 3 lines
Michal K. K. Piotrowski LTG - Linux Testers Group (http://www.stardust.webpages.pl/ltg/)
Quoted 19 lines · Michal Piotrowski
Quoted 18 lines · Nick Piggin
Quoted 1 line · C.Y.M
Since I updated to 2.6.18, I have had the following warnings in my
syslog. Is
Quoted 1 line
this a known problem? Better yet, is there a solution to this? I am
running on
Quoted 6 lines
a i686 (Athlon XP) 32 bit cpu compiled under gcc-3.4.6.
Oct 5 08:27:31 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 08:27:31 sid kernel: [<c0182a10>]
set_dentry_child_flags+0x170/0x190Quoted 1 line
Oct 5 08:27:31 sid kernel: [<c0182adf>]
remove_watch_no_event+0x5f/0x70Quoted 1 line
Oct 5 08:27:31 sid kernel: [<c0182b08>]inotify_remove_watch_locked+0x18/0x50 > Oct 5 08:27:31 sid kernel: [<c01833dc>] inotify_rm_wd+0x6c/0xb0Quoted 1 line
Oct 5 08:27:31 sid kernel: [<c0183e98>]
Quoted 8 lines
Quoted 4 lines
sys_inotify_rm_watch+0x38/0x60 > Oct 5 08:27:31 sid kernel: [<c0102d8f>] syscall_call+0x7/0xbI don't think it is a known problem. Is it reproduceable?
It is a known problem.
http://www.ussg.iu.edu/hypermail/linux/kernel/0608.1/1209.html
Thank you for the confirmation. Please include me in this thread if someone finds the answer. This bug seems to occur very frequently on my machine with 2.6.18.1 so I have been forced to revert back to 2.6.17.13 until I can fix it.
Best Regards.
Quoted 40 lines · C.Y.M
Quoted 38 lines · Michal Piotrowski
Quoted 35 lines · Nick Piggin
Quoted 1 line · C.Y.M
Since I updated to 2.6.18, I have had the following warnings in my
syslog. Is
Quoted 1 line
this a known problem? Better yet, is there a solution to this? I am
running on
Quoted 6 lines
a i686 (Athlon XP) 32 bit cpu compiled under gcc-3.4.6.
Oct 5 08:27:31 sid kernel: BUG: warning at fs/inotify.c:181/set_dentry_child_flags() Oct 5 08:27:31 sid kernel: [<c0182a10>]
set_dentry_child_flags+0x170/0x190Quoted 1 line
Oct 5 08:27:31 sid kernel: [<c0182adf>]
remove_watch_no_event+0x5f/0x70Quoted 1 line
Oct 5 08:27:31 sid kernel: [<c0182b08>]
inotify_remove_watch_locked+0x18/0x50Quoted 2 lines
Oct 5 08:27:31 sid kernel: [<c01833dc>] inotify_rm_wd+0x6c/0xb0 Oct 5 08:27:31 sid kernel: [<c0183e98>]
sys_inotify_rm_watch+0x38/0x60Quoted 1 line
Oct 5 08:27:31 sid kernel: [<c0102d8f>] syscall_call+0x7/0xbI don't think it is a known problem. Is it reproduceable?
Quoted 8 lines
Quoted 3 lines
It is a known problem.
http://www.ussg.iu.edu/hypermail/linux/kernel/0608.1/1209.htmlThank you for the confirmation. Please include me in this thread if someone finds the answer. This bug seems to occur very frequently on my machine with 2.6.18.1 so I have been forced to revert back to 2.6.17.13 until I can fix it.
I haven't got around to looking at it yet, sorry.
It does seem like my inotify scalability patch is involved, however it is interesting that you cannot reproduce the problem in 2.6.17.13.
I probably won't get around to having a look at it for a while, but if you would like to speed up the process you could try running a git bisect to find which patch is making the error trigger for you.
Signature · 2 lines
SUSE Labs, Novell Inc. Send instant messages to your online friends http://au.messenger.yahoo.com
Quoted 9 lines
Quoted 8 lines
Thank you for the confirmation. Please include me in this thread if someone
finds the answer. This bug seems to occur very frequently on my machine with
2.6.18.1 so I have been forced to revert back to 2.6.17.13 until I can fix it.
Quoted 9 lines
I haven't got around to looking at it yet, sorry.
It does seem like my inotify scalability patch is involved, however it is interesting that you cannot reproduce the problem in 2.6.17.13.
I probably won't get around to having a look at it for a while, but if you would like to speed up the process you could try running a git bisect to find which patch is making the error trigger for you.
I finally got around to try 2.6.18.2 and I still seem to have this problem. Has anyone had a chance to make a patch for this yet?
Best Regards.