All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Keenan <matt@opcode-solutions.com>
To: Steve French <smfrench@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-cifs-client@lists.samba.org
Subject: Re: [PATCH] CIFS should honour umask
Date: Thu, 07 Jun 2007 18:42:24 +0100	[thread overview]
Message-ID: <46684380.7080302@opcode-solutions.com> (raw)
In-Reply-To: <524f69650706071001q30a818eepfef98010258b14f7@mail.gmail.com>

Steve French wrote:
> For the non-unix case (e.g. Windows servers) the mode will be taken
> from the default specified on the mount. I am not sure if we also
> should add code to also honor umask in that case.
>
I don't think it would be necessary to add code for the windows case, we
should just rely on windows semantics (with acl if supplied) for pure
windows mounts.
> I am not sure how common it is to change umask to different values in
> different processes which would access the same mount.
>
I think if we are going to use umask we should use it the way it is used
in Unix, i.e. tagged to the process. I realise that in some
circumstances that having a mount wide umask would be handy, however if
we are going to apply unix style semantics we should stick to the unix
style process bound umask; i.e. the method of least suprise.

Matt

-- 
Matt Keenan
OpCode Solutions

      reply	other threads:[~2007-06-07 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 19:07 [PATCH] CIFS should honour umask Matt Keenan
2007-06-07  0:23 ` Steve French
     [not found]   ` <4667AE70.7090800@opcode-solutions.com>
2007-06-07 17:01     ` Steve French
2007-06-07 17:42       ` Matt Keenan [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=46684380.7080302@opcode-solutions.com \
    --to=matt@opcode-solutions.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.