| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [bug report]: chown(2) implementation in xfs is broken |
| From: | Robert Brockway <robert@xxxxxxxxxxxxxxxxx> |
| Date: | Tue, 8 Jul 2003 11:50:15 -0400 (EDT) |
| In-reply-to: | <20030708071045.GE930@xxxxxxxxxxxxxxx> |
| References: | <7kadbrchcp.fsf@xxxxxxxxxxxxxx> <3F08C005.3070706@xxxxxxxxxxxxx> <Pine.LNX.4.56.0307070055520.11005@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030707053311.GX930@xxxxxxxxxxxxxxx> <Pine.LNX.4.56.0307070154350.11005@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030707065106.GY930@xxxxxxxxxxxxxxx> <Pine.LNX.4.56.0307071124550.21904@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030708071045.GE930@xxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Mon, 7 Jul 2003, Ethan Benson wrote: > how so? s bits are cleared on chown(2). Yes, I confirmed that the s bit was being cleared with the chown, as normal. > > Linux quite happily set restrict_chown=0 on my quota enabled xfs > > filesystem. It would definately be worth having a sanity check about > > enabling both options at once. > > did you check that chown() was still permitted? if so i would find Yep. The tests I did were all on an xfs with quota enabled and in use. > out if irix is the same. i would consider that a bug, but since its a > configurable sysctl default to a secure state its not really that big > a deal, if root wants to shoot himself in the foot, let him. nuke(8) ;) [1] [1] From the ASR man pages. Rob -- Robert Brockway B.Sc. email: robert@xxxxxxxxxxxxxxxxx ICQ: 104781119 Linux counter project ID #16440 (http://counter.li.org) "The earth is but one country and mankind its citizens" -Baha'u'llah |
| Previous by Date: | SW raid5 & loop device & log problem, Ing. Milan Kocian |
|---|---|
| Next by Date: | TAKE - merge up the 1.3 tree, Russell Cattelan |
| Previous by Thread: | Re: [bug report]: chown(2) implementation in xfs is broken, Ethan Benson |
| Next by Thread: | Re: [bug report]: chown(2) implementation in xfs is broken, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |