From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932969AbXCHKMY (ORCPT ); Thu, 8 Mar 2007 05:12:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932973AbXCHKMY (ORCPT ); Thu, 8 Mar 2007 05:12:24 -0500 Received: from mail.suse.de ([195.135.220.2]:42596 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932969AbXCHKMX (ORCPT ); Thu, 8 Mar 2007 05:12:23 -0500 Subject: Re: Null pointer in autofs4 (_spin_lock) in 2.6.21-rc2 From: Thomas Renninger Reply-To: trenn@suse.de To: Andrew Morton Cc: linux-kernel@vger.kernel.org, Ian Kent In-Reply-To: <20070308012844.025794e3.akpm@linux-foundation.org> References: <1173344276.5863.21.camel@queen.suse.de> <20070308012844.025794e3.akpm@linux-foundation.org> Content-Type: text/plain Organization: Novell/SUSE Date: Thu, 08 Mar 2007 11:12:16 +0100 Message-Id: <1173348736.5863.23.camel@queen.suse.de> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2007-03-08 at 01:28 -0800, Andrew Morton wrote: > > On Thu, 08 Mar 2007 09:57:56 +0100 Thomas Renninger wrote: > > I saw this happening several times on 2.6.21-rc2. > > Tell me how I can help... > > Some nfs partitions are mounted via nfs using autofs. > > It takes some hours to run into this: > > > > Unable to handle kernel NULL pointer dereference at 0000000000000008 > > RIP: > > [] _spin_lock+0x0/0xf > > PGD 1dde23067 PUD 1d3060067 PMD 0 > > Oops: 0002 [1] SMP > > CPU 3 > > Modules linked in: autofs4 nfs lockd nfs_acl sunrpc asus_acpi af_packet > > tg3 ipv6 button battery ac ext2 mbcache loop dm_mod floppy parport_pc lp > > parport reiserfs pata_amd edd fan thermal sg processor sata_sil libata > > amd74xx sd_mod scsi_mod ide_disk ide_core > > Pid: 11373, comm: touch Not tainted 2.6.21-rc2-default #6 > > RIP: 0010:[] [] _spin_lock+0x0/0xf > > RSP: 0018:ffff8101c50a5a50 EFLAGS: 00010202 > > RAX: ffff8100eb8916f8 RBX: ffff81010007dcd8 RCX: ffff8100ea45b280 > > RDX: 0000000010e58c2e RSI: ffff810163bf9e50 RDI: 0000000000000008 > > RBP: ffff810163bf9e50 R08: ffff8101c50a4000 R09: ffff8101c50a5ea8 > > R10: ffff81010003fca8 R11: ffffffff802299ad R12: 0000000000000000 > > R13: ffff8100eb891680 R14: 0000000000000005 R15: ffff8101c50a5b48 > > FS: 00002b8ae744bf20(0000) GS:ffff81010016a7c0(0000) > > knlGS:00000000b7bd88d0 > > CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > > CR2: 0000000000000008 CR3: 00000001b925f000 CR4: 00000000000006e0 > > Process touch (pid: 11373, threadinfo ffff8101c50a4000, task > > ffff8101b78bd100) > > Stack: ffffffff882d5f38 ffff8101c50a5ea8 ffff8100ec8df4b0 > > 00000000000000d0 > > ffff8100eb8916f8 ffff810163bf9efc 10e58c2eea45b220 ffff8100ea45b220 > > ffff810163bf9e50 ffff8100ea45b220 ffff8100ec8df4b0 ffff8100ec8df568 > > Call Trace: > > [] :autofs4:autofs4_lookup+0xcb/0x311 > > [] do_lookup+0xc4/0x1ae > > [] __link_path_walk+0x8ec/0xd9d > > [] :sunrpc:rpcauth_lookup_credcache+0x12e/0x24a > > [] link_path_walk+0x58/0xe0 > > [] __strncpy_from_user+0x17/0x41 > > [] __link_path_walk+0x5c9/0xd9d > > [] link_path_walk+0x58/0xe0 > > [] __strncpy_from_user+0x17/0x41 > > [] do_path_lookup+0x1b6/0x217 > > [] __path_lookup_intent_open+0x56/0x97 > > [] open_namei+0xa9/0x64c > > [] do_page_fault+0x45e/0x7ad > > [] do_filp_open+0x1c/0x38 > > [] __strncpy_from_user+0x17/0x41 > > [] do_sys_open+0x44/0xc1 > > [] system_call+0x7e/0x83 > > > > > > Code: f0 ff 0f 79 09 f3 90 83 3f 00 7e f9 eb f2 c3 f0 81 2f 00 00 > > RIP [] _spin_lock+0x0/0xf > > RSP > > CR2: 0000000000000008 > > I assume 2.6.20 is OK? Can't say for sure, I expect yes. Set up with 2.6.20 now and let it run for a day or two. Maybe someone has worked in that area and has an idea meanwhile... Thomas