| To: | Andi Kleen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: SPEC failures |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | Wed, 15 Aug 2001 14:34:21 -0500 |
| Cc: | Steve Lord <lord@xxxxxxx>, Ken Cross <kcross@xxxxxxxxx>, Linux XFS <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | Message from Andi Kleen <ak@suse.de> of "Wed, 15 Aug 2001 19:54:24 +0200." <20010815195424.A22872@gruyere.muc.suse.de> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
> On Wed, Aug 15, 2001 at 10:30:46AM -0500, Steve Lord wrote: > > Andrew had the approach of setting the umask of the nfsd process to 0 at > > startup, there was some other reason for this not being popular. > > He did it for init_task, which disturbed all other kernel threads too > and opened tons of security holes. > The right way IMHO is to give nfsd an own fs_struct and set umask there, > as in this patch. > > -Andi Thanks, Care to try this one on Neil Brown or Trond? I wonder if the acl project has run into the same issue? The tricky part in justifying this is nothing in the main kernel needs this change right now. Steve |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: error in xfs_logprint?, Eric Sandeen |
|---|---|
| Next by Date: | Error compiling 2.4.9-pre4-xfs, Ken Cross |
| Previous by Thread: | Re: SPEC failures, Andi Kleen |
| Next by Thread: | Re: SPEC failures, Timothy Shimmin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |