From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from mail.candelatech.com ([208.74.158.172]:60972 "EHLO ns3.lanforge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751119Ab3ARVgm (ORCPT ); Fri, 18 Jan 2013 16:36:42 -0500 Message-ID: <50F9C069.8070106@candelatech.com> Date: Fri, 18 Jan 2013 13:36:41 -0800 From: Ben Greear MIME-Version: 1.0 To: Chuck Lever CC: "linux-nfs@vger.kernel.org" Subject: Re: Question on nfs40_discover_server_trunking. References: <50F9BE66.6080608@candelatech.com> <0F001F0E-229D-4314-A42E-84402E4F1FC7@oracle.com> In-Reply-To: <0F001F0E-229D-4314-A42E-84402E4F1FC7@oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: On 01/18/2013 01:33 PM, Chuck Lever wrote: > > On Jan 18, 2013, at 4:28 PM, Ben Greear wrote: > >> Any chance the STALE_CLIENTID case needs a 'break'? > > I don't think so. LEASE_CONFIRM is set, and we want to wake the state renewal thread. > >> >> Twice I've seen kernel crashes after the nfs40_walk_client_list >> failed (though code comments say it should never fail). > > nfs40_walk_client_list() is looking for an nfs_client that is supposed to already be in the nfs_client list. If the search fails, that's a bug. > > Eyeball the contents of your nfs_client list. You should find an appropriate nfs_client in there, and then figure out why the search doesn't find it. Ok, I'll keep poking at the code. My test case is 3000 individual mounts, and the system is working very hard, so not sure eyeballing printk's is going to help a whole lot :) Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com