From: Marek Habersack <grendel@debian.org>
To: Christoph Hellwig <hch@infradead.org>, Steve Lord <lord@sgi.com>,
Arjan van de Ven <arjanv@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.73-mm1 XFS] restrict_chown and quotas
Date: Wed, 25 Jun 2003 17:39:43 +0200 [thread overview]
Message-ID: <20030625153943.GJ1745@thanes.org> (raw)
In-Reply-To: <20030625161627.A20049@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On Wed, Jun 25, 2003 at 04:16:27PM +0100, Christoph Hellwig scribbled:
[snip]
> > at Irix and confirm this. Imposing different semantics on the rest of
> > the filesystems did not seem like the right thing to do.
>
> Actually there's a posix option group for finding out exactly that,
> (see http://people.redhat.com/drepper/posix-option-groups.html#CHOWN_RESTRICTED)
> but yeah it might be more of a legacy thing.
>
> Adding a common sysctl for this would allow glibc to properly implement
> patchconf(..., _PC_CHOWN_RESTRICTED), but it seems SuSv2/3 sais it must
> be always defined:
>
> http://www.opengroup.org/onlinepubs/007908799/xsh/chown.html
This being clear, maybe it should be a compile-time option in XFS? Or
would that be unacceptable?
marek
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-25 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 9:51 [2.5.73-mm1 XFS] restrict_chown and quotas Marek Habersack
2003-06-25 12:51 ` Steve Lord
2003-06-25 13:41 ` Marek Habersack
2003-06-25 14:25 ` Arjan van de Ven
2003-06-25 14:35 ` Christoph Hellwig
2003-06-25 15:11 ` Steve Lord
2003-06-25 15:16 ` Christoph Hellwig
2003-06-25 15:25 ` Steve Lord
2003-06-26 2:00 ` jw schultz
2003-06-25 15:39 ` Marek Habersack [this message]
2003-06-25 15:56 ` Christoph Hellwig
2003-06-25 15:11 ` Valdis.Kletnieks
2003-06-25 15:46 ` Marek Habersack
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=20030625153943.GJ1745@thanes.org \
--to=grendel@debian.org \
--cc=arjanv@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@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