Subject: Re: bug with chown with kernel 2.6.0-test1?
From: Eric Sandeen <sandeen@sgi.com>
To: marc@mco.mine.nu
Cc: linux-xfs@oss.sgi.com
In-Reply-To: <200307281831.28840.marc@mco.mine.nu>
References: <200307281831.28840.marc@mco.mine.nu>
Content-Type: text/plain
Organization: 
Message-Id: <1059411469.28137.17.camel@stout.americas.sgi.com>
Mime-Version: 1.0
Date: 28 Jul 2003 11:57:50 -0500
Content-Transfer-Encoding: 7bit
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk
Content-Length: 1337
Lines: 46

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.

-eric

On Mon, 2003-07-28 at 11:31, Marc Cousin wrote:
> I don't know if :
> - This is the right place to report it
> - It is a bug 
> 
> I am having strange chown behaviour
> 
> all the operations below are done as root
> -------------------------------------------------------
> I first try it whith restrict chown to 1
> 
> fs.xfs.stats_clear = 0
> fs.xfs.sync_interval = 30000
> fs.xfs.error_level = 3
> fs.xfs.panic_mask = 0
> fs.xfs.irix_symlink_mode = 0
> fs.xfs.irix_sgid_inherit = 0
> fs.xfs.restrict_chown = 1
> marco:/dvdrip# touch test
> marco:/dvdrip# chown marc test
> chown: changing ownership of `test': Operation not permitted
> -----------------------------------------------------
> then with restrict chown to 0
> marco:/dvdrip# touch test
> marco:/dvdrip# chown marc test
> marco:/dvdrip# chown root test
> chown: changing ownership of `test': Operation not permitted
> 
> 
> I don't think this is a normal behaviour (in either case), but the restrict 
> chown is confusing me a little bit ...
> 
> 
> 
> Meanwhile, I'm going to install 2.6.0-test2... :)
-- 
Eric Sandeen      [C]XFS for Linux   http://oss.sgi.com/projects/xfs
sandeen@sgi.com   SGI, Inc.          651-683-3102