From: Greg Banks <gnb@sgi.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: reiserfs-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
ecryptfs-devel@lists.sourceforge.net, nfs@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, unionfs@filesystems.org,
linux-cifs-client@lists.samba.org
Subject: Re: [NFS] [PATCH 2/7] NFS: if ATTR_KILL_S*ID bits are set, then skip mode change
Date: Sat, 15 Sep 2007 01:43:45 +1000 [thread overview]
Message-ID: <20070914154345.GE25610@sgi.com> (raw)
In-Reply-To: <20070914105838.efbfc45e.jlayton@redhat.com>
On Fri, Sep 14, 2007 at 10:58:38AM -0400, Jeff Layton wrote:
> On Sat, 15 Sep 2007 00:40:33 +1000
> Greg Banks <gnb@sgi.com> wrote:
>
>
> > Ok, you convinced me.
>
> Right. When I was first looking at this, I considered some similar
> approaches, but hit roadblocks with all of them. The only real option
> seems to be to leave this to the server, but that does assume that the
> server handles this properly.
>
> Servers that don't are broken, IMO.
According to what spec? A quick trip around the machine room shows
that neither Solaris 10 nor Darwin 7.9.0 clobber setuid on write
either.
> If Irix isn't clearing these bits
> on a write then it might be good to see if they can fix that...
I think first you'd have to mount a serious argument that it's broken,
more serious than "it works differently from Linux".
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
Apparently, I'm Bedevere. Which MPHG character are you?
I don't speak for SGI.
next prev parent reply other threads:[~2007-09-14 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 14:37 [PATCH 2/7] NFS: if ATTR_KILL_S*ID bits are set, then skip mode change Jeff Layton
2007-09-14 10:25 ` [NFS] " Greg Banks
2007-09-14 11:02 ` Jeff Layton
2007-09-14 13:09 ` Greg Banks
2007-09-14 13:38 ` Jeff Layton
2007-09-14 14:40 ` [NFS] " Greg Banks
2007-09-14 14:58 ` Jeff Layton
2007-09-14 15:43 ` Greg Banks [this message]
2007-09-14 16:01 ` Jeff Layton
2007-09-17 13:10 ` Trond Myklebust
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=20070914154345.GE25610@sgi.com \
--to=gnb@sgi.com \
--cc=ecryptfs-devel@lists.sourceforge.net \
--cc=jlayton@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=reiserfs-devel@vger.kernel.org \
--cc=unionfs@filesystems.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).