xfs
[Top] [All Lists]

Re: bug with chown with kernel 2.6.0-test1?

To: linux-xfs@xxxxxxxxxxx
Subject: Re: bug with chown with kernel 2.6.0-test1?
From: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Mon, 28 Jul 2003 23:20:15 -0800
In-reply-to: <1059411469.28137.17.camel@stout.americas.sgi.com>
Mail-copies-to: nobody
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <200307281831.28840.marc@mco.mine.nu> <1059411469.28137.17.camel@stout.americas.sgi.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Mon, Jul 28, 2003 at 11:57:50AM -0500, Eric Sandeen wrote:
> restrict_chown (the default) means that only root can "give away" files
> to another user via chown.
> 
> But yes, this does look like a bug.

what does? appears to be correct behavior to me:

> > fs.xfs.restrict_chown = 1
> > marco:/dvdrip# touch test
> > marco:/dvdrip# chown marc test
> > chown: changing ownership of `test': Operation not permitted

marco != root && marco != marc, chown not permitted.

> > -----------------------------------------------------
> > then with restrict chown to 0
> > marco:/dvdrip# touch test
> > marco:/dvdrip# chown marc test

!restrict_chown, this chown permitted.

> > marco:/dvdrip# chown root test
> > chown: changing ownership of `test': Operation not permitted

marco != root && marco != marc which is now the owner of the file, due
to previous chown, you can't chown a file you don't own under any
circumstances.  chown not permitted.

> > 
> > I don't think this is a normal behaviour (in either case), but the restrict 
> > chown is confusing me a little bit ...

looks normal and correct to me.

maybe im missing something.

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

Attachment: pgprNPSFHG9bQ.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>