| To: | Robert Brockway <robert@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [bug report]: chown(2) implementation in xfs is broken |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | 07 Jul 2003 09:14:11 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.56.0307070154350.11005@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Organization: | |
| References: | <7kadbrchcp.fsf@xxxxxxxxxxxxxx> <3F08C005.3070706@xxxxxxxxxxxxx> <Pine.LNX.4.56.0307070055520.11005@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030707053311.GX930@xxxxxxxxxxxxxxx> <Pine.LNX.4.56.0307070154350.11005@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Mon, 2003-07-07 at 00:59, Robert Brockway wrote: > Is the option there for compatability with Irix, and if so, why does Irix > allow it? It is there for Irix compatibility, as are a few of the other sysctls. I don't know the details of why it is an option on Irix. You're right that it can be abused... but the (correct) default is secure, and only root can change it. I suppose we could be clever about it and make a CONFIG_PURE_LINUX_XFS_BEHAVIORS config option, and hardcode it at at compile time. But I think that's getting pretty close to feature-itis. :) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc. 651-683-3102 |
| Previous by Date: | question about xfs_trans_dup function in xfs code, jin hee park |
|---|---|
| Next by Date: | Re: [bug report]: chown(2) implementation in xfs is broken, Robert Brockway |
| Previous by Thread: | Re: [bug report]: chown(2) implementation in xfs is broken, Robert Brockway |
| Next by Thread: | Re: [bug report]: chown(2) implementation in xfs is broken, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |