Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758284Ab1FVSV1 (ORCPT ); Wed, 22 Jun 2011 14:21:27 -0400 Received: from mail-gy0-f174.google.com ([209.85.160.174]:36625 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757743Ab1FVSV0 (ORCPT ); Wed, 22 Jun 2011 14:21:26 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=HwxodB4BYhX9ismbYOA+tcbG5KPA9J9JfiJAGNOdp6K27IcTOrJ+dY9XKzKxN8c90J jR5P51SBmAIuXz2CU0AMPcDwnGPjgtZb6NBGfSih4a3yPK09+ZLjbdv53Fk3592o1lXw GjpCCYl6ufdta3xQ2x8GeHobBktUjaAELZkaU= MIME-Version: 1.0 Date: Wed, 22 Jun 2011 11:21:25 -0700 Message-ID: Subject: Issue with Race Condition on NFS4 with KRB From: Joshua Scoggins To: linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2269 Lines: 49 Hello, We are trying to update our linux images in our CS lab and have it a bit of an issue. We are using nfs to load user home folder. While testing the new image we found that the nfs4 module will crash when using firefox 3.6.17 for an extended period of time. Some research via google yielded that it's a potential race condition specific to nfs with krb auth with newer kernels. Our old image doesn't have this issue and it seems that its due to it running a far older kernel version. We have two images and both are having this problem. One is running 2.6.39 and the other is 2.6.38. Here is what dmesg spit out from the machine running 2.6.39 on one occasion: [ 678.632061] ------------[ cut here ]------------ [ 678.632068] WARNING: at net/sunrpc/clnt.c:1567 call_decode+0xb2/0x69c() [ 678.632070] Hardware name: OptiPlex 755 [ 678.632072] Modules linked in: nvidia(P) scsi_wait_scan [ 678.632078] Pid: 3882, comm: kworker/0:2 Tainted: P 2.6.39-gentoo-r1 #1 [ 678.632080] Call Trace: [ 678.632086] [] warn_slowpath_common+0x80/0x98 [ 678.632091] [] ? nfs4_xdr_dec_readdir+0xba/0xba [ 678.632094] [] warn_slowpath_null+0x15/0x17 [ 678.632097] [] call_decode+0xb2/0x69c [ 678.632101] [] __rpc_execute+0x78/0x24b [ 678.632104] [] ? rpc_execute+0x41/0x41 [ 678.632107] [] rpc_async_schedule+0x10/0x12 [ 678.632111] [] process_one_work+0x1d9/0x2e7 [ 678.632114] [] worker_thread+0x133/0x24f [ 678.632118] [] ? manage_workers+0x18d/0x18d [ 678.632121] [] kthread+0x7d/0x85 [ 678.632125] [] kernel_thread_helper+0x4/0x10 [ 678.632128] [] ? kthread_worker_fn+0x13a/0x13a [ 678.632131] [] ? gs_change+0xb/0xb [ 678.632133] ---[ end trace 6bfae002a63e020e ]--- Is there some sort of work around? Thank you in advance Joshua Scoggins -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/