From: "Frank Filz" <ffilzlnx@mindspring.com>
To: "'Bruce Fields'" <bfields@fieldses.org>
Cc: "'Kernel NFS List'" <linux-nfs@vger.kernel.org>,
"'Ganesha NFS List'" <nfs-ganesha-devel@lists.sourceforge.net>
Subject: RE: pynfs updates
Date: Mon, 30 Sep 2013 19:54:52 -0400 [thread overview]
Message-ID: <003f01cebe38$75436480$5fca2d80$@mindspring.com> (raw)
In-Reply-To: <20130930221126.GD26382@fieldses.org>
> Thanks! A few questions:
>
> - "4.1 server tests: Fix some exception handling": could you
> include in the changelog and explanation of what problem this
> fixes? (And ditto, maybe, for the following commit?)
Ok, I'll re-examine those. They were some things I stumbled on as I tried to
resolve some other issues with pynfs.
> - "Fix SEQ9d to work in home directory instead of root": did you
> intend to include the chunk in nfs4.1/nfs4lib.py? It looks
> irrelevant.
Hmm, will fix that.
> - "Add two SECINFO_NO_NAME tests for
> SECINFO_STYLE4_PARENT":
> - SECNN3: is / required to have no parent? (I'd assumed
> here that it would also be OK to follow the convention
> that / is its own parent, but I'll admit to not having
> thought about this much.)
>From LOOKUPP:
18.14.3. DESCRIPTION
The current filehandle is assumed to refer to a regular directory or
a named attribute directory. LOOKUPP assigns the filehandle for its
parent directory to be the current filehandle. If there is no parent
directory, an NFS4ERR_NOENT error must be returned. Therefore,
NFS4ERR_NOENT will be returned by the server when the current
filehandle is at the root or top of the server's file tree.
>From SECINFO_NO_NAME:
18.45.3. DESCRIPTION
...
If the style selected is SECINFO_STYLE4_PARENT,
then SECINFO should apply the same access methodology used for
LOOKUPP when evaluating the traversal to the parent directory.
...
If SECINFO_STYLE4_PARENT is specified and there is no parent
directory, SECINFO_NO_NAME MUST return NFS4ERR_NOENT.
> - SECNN4: is env.home necessarily unequal to "/"? Would
> seem better to do the lookup in a subdirectory just to
> be certain.
Env.home is the directory you specify on the command line, I think the
presumption is that it is a writeable file system. Pynfs creates tmp and
tree directories in home (and maybe some files also?). Guess if / was
writeable, you could specify /, so yea, maybe it should go into tmp.
A better test might actually be to do LOOKUP down to home and even into tmp,
looking for a junction, and then do the SECINFO_NO_NAME(parent) on the
directory handle just across the junction if one was found.
Thanks for the review.
Frank
next prev parent reply other threads:[~2013-09-30 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 18:17 pynfs updates Frank Filz
2013-09-30 22:11 ` Bruce Fields
2013-09-30 23:54 ` Frank Filz [this message]
2013-10-01 14:26 ` 'Bruce Fields'
2013-10-01 14:30 ` 'Bruce Fields'
2013-10-01 15:42 ` Frank Filz
2013-10-01 19:05 ` Frank Filz
2013-10-02 11:36 ` 'Bruce Fields'
2013-10-02 15:58 ` Frank Filz
2013-10-01 18:21 ` Frank Filz
2013-10-01 18:45 ` '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='003f01cebe38$75436480$5fca2d80$@mindspring.com' \
--to=ffilzlnx@mindspring.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfs-ganesha-devel@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;
as well as URLs for NNTP newsgroup(s).