xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: fchown permission check bug

from [Jakob Østergaard] [Permanent Link][Original]
To: Steve Lord <lord@xxxxxxx>
Subject: Re: fchown permission check bug
From: Jakob Østergaard <joe@xxxxxxxxxxxx>
Date: Mon, 27 Mar 2006 18:06:57 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <442809EF.2010009@xxxxxxx>
Organization: Evalesco Systems ApS
References: <4427BEFD.5060509@xxxxxxxxxxxx> <442809EF.2010009@xxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5 (X11/20051201) 
Steve Lord wrote:
Check the value of /proc/sys/fs/xfs/restrict_chown, this should be 1 to enable 
this.


# cat /proc/sys/fs/xfs/restrict_chown
1
That's how it is, on the affected machine. Should it be 0? Is there any good reason why XFS by default behaves differently from ext3 on this? (As a naïve user I'd expect CAP_CHOWN to allow fchown ;) 

Thanks,

--
Best regards,
   Jakob Oestergaard
   [The SysOrb Team]
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: How many people regularly defrag their XFS filesystems?, Eric Sandeen
Next by Date:  exclusion of trees with xfsdump, Rumi Szabolcs
Previous by Thread:  Re: fchown permission check bug, Steve Lord
Next by Thread:  Re: fchown permission check bug, Steve Lord
Indexes:  [Date] [Thread] [Top] [All Lists]