From: Neil Brown <neilb@suse.de>
To: Frank Filz <ffilzlnx@us.ibm.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
ffilz@us.ibm.com, nfs@lists.sourceforge.net,
Steve Dickson <SteveD@redhat.com>
Subject: Re: [NFS] nfs-utils crossmnt/fsid bug
Date: Tue, 4 Dec 2007 12:09:26 +1100 [thread overview]
Message-ID: <18260.43206.943331.889058@notabene.brown> (raw)
In-Reply-To: message from Frank Filz on Monday December 3
On Monday December 3, ffilzlnx@us.ibm.com wrote:
> On Fri, 2007-11-23 at 13:50 +1100, Neil Brown wrote:
> > Does this (untested, but it compiles) patch seem right?
>
> In testing security negotiation, I ran into this problem. I've tried
> this patch and it doesn't seem to be working right. My exports file is:
>
> /export/home gss/krb5i(nohide,insecure,no_subtree_check,no_root_squash,async,rw)
> /export/home gss/krb5p(nohide,insecure,no_subtree_check,no_root_squash,async,rw)
> /export gss/krb5(fsid=0,insecure,no_subtree_check,no_root_squash,async,rw,crossmnt)
> /export gss/krb5i(fsid=0,insecure,no_subtree_check,no_root_squash,async,rw,crossmnt)
You don't need the patch for this exports file. It is only relevant
when the underlying filesystem is not explicitly exported, so the
export flags a deduced implicitly.
So - this is a separate issue.
>
> From the client I execute:
>
> mount -overs=4,sec=krb5 elm3a19.beaverton.ibm.com:/ /mnt
> ls -l /mnt/home
... and what happens?
NeilBrown
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2007-12-04 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 20:46 nfs-utils crossmnt/fsid bug J. Bruce Fields
2007-11-23 2:50 ` [NFS] " Neil Brown
[not found] ` <18246.16373.177320.570040-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-11-26 22:39 ` J. Bruce Fields
2007-11-29 3:59 ` Neil Brown
2007-12-03 22:51 ` Frank Filz
2007-12-04 1:09 ` Neil Brown [this message]
[not found] ` <18260.43206.943331.889058-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-12-04 17:42 ` Frank Filz
2007-12-07 19:05 ` Frank Filz
2007-12-11 21:20 ` Frank Filz
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=18260.43206.943331.889058@notabene.brown \
--to=neilb@suse.de \
--cc=SteveD@redhat.com \
--cc=bfields@fieldses.org \
--cc=ffilz@us.ibm.com \
--cc=ffilzlnx@us.ibm.com \
--cc=nfs@lists.sourceforge.net \
/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