Linux NFS development
 help / color / mirror / Atom feed
From: "Frank Filz" <ffilzlnx@mindspring.com>
To: <linux-nfs@vger.kernel.org>
Subject: Execute only permission issue with client
Date: Wed, 25 Jun 2014 14:56:25 -0700	[thread overview]
Message-ID: <029301cf90c0$4fabe660$ef03b320$@mindspring.com> (raw)

Back a year ago or so, I ran the following test against Ganesha:

http://www.tuxera.com/community/posix-test-suite/

On NFS v4, one of the issues it tripped over was execute only files.
Apparently the Linux v4 client doesn't make ACCESS calls in conjunction with
an open system call, with the result that you can open an execute only file
(per RFC 3530bis, the server is allowing such to allow clients to execute
executables).

We tripped over this issue again in some of our testing.

One bit that I don't actually understand is how the kernel differentiates
between bash (etc) issuing an open system call to load a script and vi
trying to browse same script... 

I had done some testing executing shell scripts and such and saw some
inconsistency. Now, trying things, I can't seem to run a bash script that is
execute only (local, v3, or v4), but can run a compiled binary that is
execute only (local, v3, and v4), so I'm not sure what the deal is...

Current setup is Fedora 20 with EXT4, running Ganesha 2.1 for NFS server.

Thanks for any insight,

Frank





             reply	other threads:[~2014-06-25 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 21:56 Frank Filz [this message]
2014-06-25 22:21 ` Execute only permission issue with client Trond Myklebust
2014-06-25 22:29   ` Frank Filz
2014-06-25 22:34     ` Trond Myklebust
2014-06-25 22:41       ` Frank Filz
2014-07-01 19:10       ` Frank Filz
2014-07-01 20:13         ` Trond Myklebust
2014-07-01 20:28           ` 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='029301cf90c0$4fabe660$ef03b320$@mindspring.com' \
    --to=ffilzlnx@mindspring.com \
    --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