From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750720AbVHUGkf (ORCPT ); Sun, 21 Aug 2005 02:40:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750774AbVHUGke (ORCPT ); Sun, 21 Aug 2005 02:40:34 -0400 Received: from tornado.reub.net ([202.89.145.182]:23227 "EHLO tornado.reub.net") by vger.kernel.org with ESMTP id S1750720AbVHUGke (ORCPT ); Sun, 21 Aug 2005 02:40:34 -0400 Message-ID: <430821E1.8040308@reub.net> Date: Sun, 21 Aug 2005 18:40:33 +1200 From: Reuben Farrelly User-Agent: Thunderbird 1.6a1 (Windows/20050820) MIME-Version: 1.0 To: Andrew Morton CC: linux-kernel@vger.kernel.org Subject: Re: 2.6.13-rc6-mm1 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 19/08/2005 11:37 a.m., Andrew Morton wrote: > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc6/2.6.13-rc6-mm1/ > > - Lots of fixes, updates and cleanups all over the place. > > - If you have the right debugging options set, this kernel will generate > a storm of sleeping-in-atomic-code warnings at boot, from the scsi code. > It is being worked on. > > > Changes since 2.6.13-rc5-mm1: > > linus.patch Noted this in my log earlier today. Is this inotify related? Aug 21 08:33:04 tornado kernel: idr_remove called for id=2048 which is not allocated. Aug 21 08:33:04 tornado kernel: [] dump_stack+0x17/0x19 Aug 21 08:33:04 tornado kernel: [] idr_remove_warning+0x1b/0x1d Aug 21 08:33:04 tornado kernel: [] sub_remove+0x88/0xea Aug 21 08:33:04 tornado kernel: [] idr_remove+0x1b/0x7f Aug 21 08:33:04 tornado kernel: [] remove_watch_no_event+0x7a/0x12e Aug 21 08:33:04 tornado kernel: [] inotify_release+0x8f/0x1af Aug 21 08:33:04 tornado kernel: [] __fput+0xaf/0x199 Aug 21 08:33:04 tornado kernel: [] fput+0x22/0x3b Aug 21 08:33:04 tornado kernel: [] filp_close+0x41/0x67 Aug 21 08:33:04 tornado kernel: [] sys_close+0x70/0x92 Aug 21 08:33:04 tornado kernel: [] sysenter_past_esp+0x54/0x75 Aug 21 08:33:04 tornado kernel: idr_remove called for id=3072 which is not allocated. Aug 21 08:33:05 tornado kernel: [] dump_stack+0x17/0x19 Aug 21 08:33:05 tornado kernel: [] idr_remove_warning+0x1b/0x1d Aug 21 08:33:05 tornado kernel: [] sub_remove+0x88/0xea Aug 21 08:33:05 tornado kernel: [] idr_remove+0x1b/0x7f Aug 21 08:33:05 tornado kernel: [] remove_watch_no_event+0x7a/0x12e Aug 21 08:33:05 tornado kernel: [] inotify_release+0x8f/0x1af Aug 21 08:33:05 tornado kernel: [] __fput+0xaf/0x199 Aug 21 08:33:05 tornado kernel: [] fput+0x22/0x3b Aug 21 08:33:05 tornado kernel: [] filp_close+0x41/0x67 Aug 21 08:33:05 tornado kernel: [] sys_close+0x70/0x92 Aug 21 08:33:05 tornado kernel: [] sysenter_past_esp+0x54/0x75 This would have been triggered by using dovecot IMAP which is configured to use inotify on Maildir. I'm also seeing some userspace errors logged for dovecot: "Aug 21 04:17:22 Error: IMAP(reuben): inotify_rm_watch() failed: Invalid argument" I'll deal with those with the guy who wrote the inotify code in dovecot. I'm not so sure userspace should be able or need to cause the kernel to dump stack traces like that though? reuben