Return-Path: linux-nfs-owner@vger.kernel.org Received: from mx1.redhat.com ([209.132.183.28]:51389 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751600Ab3CYUWX (ORCPT ); Mon, 25 Mar 2013 16:22:23 -0400 Message-ID: <5150B1FD.1070405@RedHat.com> Date: Mon, 25 Mar 2013 16:22:21 -0400 From: Steve Dickson MIME-Version: 1.0 To: "J. Bruce Fields" CC: Linux NFS Mailing list Subject: Re: [PATCH] mountd: regression in crossmounts References: <1364049149-3751-1-git-send-email-steved@redhat.com> <20130325181314.GA10120@fieldses.org> In-Reply-To: <20130325181314.GA10120@fieldses.org> Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-nfs-owner@vger.kernel.org List-ID: On 25/03/13 14:13, J. Bruce Fields wrote: > On Sat, Mar 23, 2013 at 10:32:29AM -0400, Steve Dickson wrote: >> commit 8e2fb3fc cause a regression in mount export >> that are on different local file system. >> Exports like (all on different filesystems) >> >> /home *(rw,fsid=0,crossmnt) >> /home/fs1 *(rw,crossmnt) >> /home/fs1/fs2/fs3 *(rw,nohide) >> >> and then a mount of the root 'mount /home /mnt' >> would end up mounting /home/fs1/fs2/fs3 not /home > > That's strange. Yeah... I had this guy reporting from day one that the latest nfs-utils broke his export world... > >> Reverting the logic of commit 8e2fb3fc until >> a better solution can be found for the original >> problem. > > I can't figure out why the patch below would help. The only change I > can see is to the way that an export of "/" would be handled. The reason I didn't debug this further was I did not know how to reproduce the original problem the patch was trying to fix... steved.