Messages in this thread | | | Subject | Re: [2.5.73-mm1 XFS] restrict_chown and quotas | From | Arjan van de Ven <> | Date | 25 Jun 2003 16:25:44 +0200 |
| |
On Wed, 2003-06-25 at 15:41, Marek Habersack wrote: > On Wed, Jun 25, 2003 at 07:51:43AM -0500, Steve Lord scribbled: > [snip] > > > For me both of the described situations seem to be a bug, but I might be > > > unaware of the rationale behind the functionality. If this is supposed to be > > > that way, maybe at least it would be better to default restrict_chown to > > > enabled initially? The behavior with restrict_chown is totally different to > > > what users/administrators are used to and, as shown in the debian package > > > build case, it might cause problems in usual situations. Also the quota > > > issue is likely to be an excellent tool for local DoS. > > > So, am I wrong in thinking that it's a bug (or at least the quota part of > > > it) or not? > > > > Sorry about this, the defaults for the systunes have been messed up > > recently. This is supposed to be on by default, irix_sgid_inherit > > is on, but should be off by default. > > > > You can switch the behavior with /proc/sys/fs/xfs/restrict_chown > > and irix_sgid_inherit. > Yep, that's what I did. I was just caught by surprise discovering the new > behavior :) and it if it was to be the default, it would have created a big > problem for distributions compatibility-wise. > > > You can also edit xfs_globals.c to switch the default at boot time. > > We will switch it back in the next update to Linus. > Great, that's good enough. > > > As for the quota operation, the normal chown situation is going > > from root to another id, and in that case, you want the quota to > > go to the end user.
another question is why is this a filesystem specific option and not a generic option ? [unhandled content-type:application/pgp-signature] | |