From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-cifs-client@lists.samba.org, nfs@lists.sourceforge.net
Subject: Re: [PATCH 0/4] add killattr inode operation to allow filesystems to interpret ATTR_KILL_S*ID bits
Date: Tue, 28 Aug 2007 20:11:14 +0100 [thread overview]
Message-ID: <20070828191114.GA3419@infradead.org> (raw)
In-Reply-To: <200708271727.l7RHR36m007248@dantu.rdu.redhat.com>
Sorry for not replying to the previsious revisions, but I've been out
for on vacation.
I can't say I like this version. Now we've got callouts at two rather close
levels which is not very nice from the interface POV.
Maybe preference is for the first scheme where we simply move interpreation
of the ATTR_KILL_SUID/ATTR_KILL_SGID into the setattr routine and provide
a nice helper for the normal filesystem to use.
If people are really concerned about adding two lines of code to the
handfull of setattr operation there's a variant of this scheme that can
avoid it:
- notify_change is modified to not clear the ATTR_KILL_SUID/ATTR_KILL_SGID
but update ia_mode and the ia_valid flag to include ATTR_MODE.
- disk filesystems stay unchanged and never look at
ATTR_KILL_SUID/ATTR_KILL_SGID, but nfs can check for it and ignore
the ATTR_MODE flags and ia_valid in this case and do the right thing
on the server side.
next prev parent reply other threads:[~2007-08-28 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 17:27 [PATCH 0/4] add killattr inode operation to allow filesystems to interpret ATTR_KILL_S*ID bits Jeff Layton
2007-08-28 19:11 ` Christoph Hellwig [this message]
2007-08-28 19:31 ` Josef Sipek
2007-08-28 19:49 ` [NFS] " Trond Myklebust
2007-08-28 19:52 ` Christoph Hellwig
2007-08-28 20:09 ` Jeff Layton
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=20070828191114.GA3419@infradead.org \
--to=hch@infradead.org \
--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 \
/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