From: Steve Dickson <SteveD@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] mountd: regression in crossmounts
Date: Mon, 25 Mar 2013 16:22:21 -0400 [thread overview]
Message-ID: <5150B1FD.1070405@RedHat.com> (raw)
In-Reply-To: <20130325181314.GA10120@fieldses.org>
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.
next prev parent reply other threads:[~2013-03-25 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 14:32 [PATCH] mountd: regression in crossmounts Steve Dickson
2013-03-25 14:18 ` Steve Dickson
2013-03-25 18:13 ` J. Bruce Fields
2013-03-25 20:22 ` Steve Dickson [this message]
2013-03-25 21:27 ` J. Bruce Fields
2013-03-25 23:36 ` J. Bruce Fields
2013-03-27 13:06 ` Steve Dickson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5150B1FD.1070405@RedHat.com \
--to=steved@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).