Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757245AbXLGWeh (ORCPT ); Fri, 7 Dec 2007 17:34:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754394AbXLGWe2 (ORCPT ); Fri, 7 Dec 2007 17:34:28 -0500 Received: from smtp2.linux-foundation.org ([207.189.120.14]:55092 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752282AbXLGWe1 (ORCPT ); Fri, 7 Dec 2007 17:34:27 -0500 Date: Fri, 7 Dec 2007 14:33:19 -0800 From: Andrew Morton To: Trond Myklebust Cc: gnome42@gmail.com, linux-kernel@vger.kernel.org, bfields@fieldses.org, rjw@sisk.pl Subject: Re: 2.6.24-rc3-git4 NFS crossmnt regression Message-Id: <20071207143319.ee048955.akpm@linux-foundation.org> In-Reply-To: <1197053179.7532.23.camel@heimdal.trondhjem.org> References: <20071207040219.e231cbc7.akpm@linux-foundation.org> <1197053179.7532.23.camel@heimdal.trondhjem.org> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.20; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2080 Lines: 57 On Fri, 07 Dec 2007 13:46:19 -0500 Trond Myklebust wrote: > > On Fri, 2007-12-07 at 13:14 -0500, Shane wrote: > > On Dec 7, 2007 7:02 AM, Andrew Morton wrote: > > ... > > > > 2.6.24-rc3-git1 is last known good kernel. The problem also exists > > > > with the latest snap 2.6.24-rc4-git4. NFS server is 2.6.23-rc9 and > > > > is unchanged. > > > > > > hm, there have been no nfs changes since 2.6.24-rc4. > > > > Ok, but the problem seems to have appeared before 2.6.24-rc4. > > > > > > It is easily reproducible here, hopefully for the person who > > > > knows how to debug it too :) > > > > > > > > > > I guess a full set of the commands which you typed to reproduce this would > > > help. > > > > Server is 2.6.23-rc9 and is exporting: > > > > /dirA/dirB > > 10.10.20.0/255.255.255.0(rw,async,no_root_squash,no_subtree_check,insecure,crossmnt) > > /dirA/dirB/dirC > > 10.10.20.0/255.255.255.0(rw,async,no_root_squash,no_subtree_check,insecure) > > /dirA/dirB/dirD > > 10.10.20.0/255.255.255.0(rw,async,no_root_squash,no_subtree_check,insecure) > > > > The NFS client (Core2 SMP) 2.6.24-rc3-git4: > > > > NFS-server:/dirA/dirB /dirA/dirB nfs > > auto,rsize=16384,wsize=16384,hard,intr,users,exec,nfsvers=3,tcp,nolock,actimeo=0 > > > > Then on the client when the new kernel has booted: > > > > ls /dirA/dirB --> normal listing > > ls /dirA/dirB/dirC --> Stale NFS file handle > > ls /dirA/dirB/dirD --> Stale NFS file handle > > > > I will do a few more builds/boots and check -rc3-git2 and -rc3-git3. > > This problem has already been reported. The fix (which I'm planning on > sending to Linus soon) is appended. > That patch isn't in git://git.linux-nfs.org/pub/linux/nfs-2.6.git. In fact that tree is empty. Has something gone wrong here? -- 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/