public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: Christoph Hellwig <hch@lst.de>
Cc: nick.couchman@seakr.com, xfs@oss.sgi.com
Subject: Re: [xfs-masters] [Bug 768]  New: Move restrict_chown to mount-time option
Date: Thu, 6 Sep 2007 12:10:06 -0400	[thread overview]
Message-ID: <20070906161006.GA25035@filer.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <20070906153529.GA3062@lst.de>

On Thu, Sep 06, 2007 at 05:35:29PM +0200, Christoph Hellwig wrote:
> On Wed, Sep 05, 2007 at 11:31:54AM -0700, bugzilla-daemon@oss.sgi.com wrote:
> > We've run into a situation where it would be extremely advantageous to be able
> > to restrict_chown on certain volumes on a server but not on others.  I'm not
> > real familiar with kernel internals, programming, etc., but I'd like to suggest
> > that restrict_chown be made a mount option for an XFS filesystem instead of a
> > system-wide, sysctl/proc option.  This would allow finer control over which
> > filesystems restrict giving away files and which don't.
> 
> It's quite easily doable.  I don't have time for that right now, but if
> anyone wants to do it's just adding the option to the mount option
> parser and adding a flag to the mount structure.
 
Wouldn't making this a generic mount-option make sense? Or is it far too
low-level of a concept?

Josef 'Jeff' Sipek.

-- 
I already backed up the [server] once, I can do it again.

       reply	other threads:[~2007-09-06 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200709051831.l85IVsTR016106@oss.sgi.com>
     [not found] ` <20070906153529.GA3062@lst.de>
2007-09-06 16:10   ` Josef Sipek [this message]
2007-09-07 19:04     ` [xfs-masters] [Bug 768] New: Move restrict_chown to mount-time option Christoph Hellwig
2007-09-07 19:15       ` Josef Sipek
2007-09-08 13:18         ` Christoph Hellwig

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=20070906161006.GA25035@filer.fsl.cs.sunysb.edu \
    --to=jsipek@fsl.cs.sunysb.edu \
    --cc=hch@lst.de \
    --cc=nick.couchman@seakr.com \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox