From: Ryan Richter <ryan@tau.solarneutrino.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: mkdir disregards umask
Date: Wed, 19 Sep 2018 16:28:34 -0400 [thread overview]
Message-ID: <20180919202834.GG9100@tau.solarneutrino.net> (raw)
In-Reply-To: <20180918203852.GG1218@fieldses.org>
On Tue, Sep 18, 2018 at 04:38:52PM -0400, J. Bruce Fields wrote:
> On Wed, Sep 12, 2018 at 02:17:47PM -0400, Ryan Richter wrote:
> > All directories created over nfs have 777 permissions.
> >
> > # umask
> > 022
> > # mkdir aaaa
> > # ls -ld aaaa
> > drwxrwxrwx 2 root root 2 Sep 12 13:45 aaaa
> > # rmdir aaaa
> > # mount|grep /mnt
> > mazuelo:/home/sbio/ryan on /mnt type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=132.204.84.95,mountvers=3,mountport=38634,mountproto=udp,local_lock=none,addr=132.204.84.95)
> >
> > The same happens for regular users.
> >
> > This is a very serious bug. The server is runnig the debian stretch 4.9
> > kernel, and the client is running a vanilla 4.4.155. Is there anything
> > in the configuration causing this, or is it a kernel bug?
>
> Beats me, I can't reproduce that on a recent kernel.
>
> Does it look the same if you run the "ls -l" on the server itself?
Yes, the permissions are really like that on the server and other
clients.
This only happens with nfsv3, so we're switching everything over to
nfsv4 this week, and I won't be able to do much more testing.
-ryan
prev parent reply other threads:[~2018-09-20 2:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 18:17 mkdir disregards umask Ryan Richter
2018-09-18 20:38 ` J. Bruce Fields
2018-09-19 20:28 ` Ryan Richter [this message]
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=20180919202834.GG9100@tau.solarneutrino.net \
--to=ryan@tau.solarneutrino.net \
--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).