From: "J. Bruce Fields" <bfields@fieldses.org>
To: "David P. Quigley" <dpquigl@tycho.nsa.gov>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux NFSv4 mailing list <nfsv4@linux-nfs.org>
Subject: Re: Weird exportfs behavior
Date: Tue, 19 Jan 2010 15:48:28 -0500 [thread overview]
Message-ID: <20100119204828.GJ5694@fieldses.org> (raw)
In-Reply-To: <1263933130.2399.160.camel-88+Bj4OksMGWPftkNcioYDMZycKHmlmlfvIqQ387n9k@public.gmane.org>
On Tue, Jan 19, 2010 at 03:32:10PM -0500, David P. Quigley wrote:
> Hello,
> I'm working on a new export option for labeled nfs and I'm getting some
> really weird behavior out of exportfs. I reverted my work to see if it
> was the cause of the problem however the error still persists. For a
> while I was getting errors about exportfs not knowing about
> no_all_squashlabelloc=key so I tried to fix that and in the process I'd
> had managed to get it to ignore labelloc all together. I don't think
> that is the cause of the problems though. When I cat /var/lib/nfs/etab I
> get a really weird line.
>
> /exports *(rw,sync,wdelay,security_label,hide,nocrossmnt,insecure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,fsid=0,anonuid=65534,anongid=65534,sec=unix,rw,root_squash,no_all_squash)
>
> if you notice rw,root_squash, and no_all_squash are in that line twice.
That's normal; it also allows some flags to vary on a
per-security-flavor basis, so that last bit:
sec=unix,rw,root_squash,no_all_squash
is just telling you what their values are for the specific sec=unix
case. It's redundant but harmless.
> I can't seem to figure out where the second set of those come from. I
> believe that is causing the problem with my labelloc export because I
> can't figure out how to get the last no_all_squash to have a comma after
> it.
Looks like you have to modify both support/nfs/exports.c:putexportent()
and utils/exportfs/exportfs.c:dump(), in addition to parseopts().
(Which is really confusing. Someone should fix that..) Maybe you're
forgetting one of those?
--b.
> It seems odd to me that this is doubled and I'm guessing it might be
> a bug. I'm using the kernel and nfs-utils git hashes below.
>
> Kernel: 22763c5cf3690a681551162c15d34d935308c8d7 (with LNFS patches)
> nfs-utils: 1a1f991870f02b303a05e1d63915226e7cfb9f53 (with LNFS patches)
>
> Dave
>
> _______________________________________________
> NFSv4 mailing list
> NFSv4@linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4
next prev parent reply other threads:[~2010-01-19 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 20:32 Weird exportfs behavior David P. Quigley
[not found] ` <1263933130.2399.160.camel-88+Bj4OksMGWPftkNcioYDMZycKHmlmlfvIqQ387n9k@public.gmane.org>
2010-01-19 20:48 ` J. Bruce Fields [this message]
2010-01-19 20:59 ` David P. Quigley
[not found] ` <1263934773.2399.162.camel-88+Bj4OksMGWPftkNcioYDMZycKHmlmlfvIqQ387n9k@public.gmane.org>
2010-01-19 21:10 ` J. Bruce Fields
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=20100119204828.GJ5694@fieldses.org \
--to=bfields@fieldses.org \
--cc=dpquigl@tycho.nsa.gov \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.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