Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*umask\s+fix\s+\(patch\)\s*$/: 18 ]

Total 18 documents matching your query.

1. umask fix (patch) (score: 1)
Author: xx>
Date: Wed, 25 Jul 2001 19:24:17 -0700 (PDT)
The problem turned out to be in the nfsd code. The following fixes it: -- fs/nfsd/nfssvc.c 2001/05/29 19:53:13 1.13 +++ fs/nfsd/nfssvc.c 2001/07/26 02:27:26 @@ -150,6 +150,7 @@ MOD_INC_USE_COUNT; loc
/archives/xfs/2001-07/msg01165.html (7,220 bytes)

2. Re: umask fix (patch) (score: 1)
Author: xx>
Date: Thu, 26 Jul 2001 13:11:56 +1000
Kernel threads share the init task fs context. That change makes all future kernel threads run with umask 0, a big security exposure. This problem was supposed to have been fixed in 2.4.7-pre7.
/archives/xfs/2001-07/msg01166.html (7,950 bytes)

3. Re: umask fix (patch) (score: 1)
Author: xx>
Date: Thu, 26 Jul 2001 14:53:24 -0500
There is an XFS bug in here, I am not quite sure how to fix it at the moment though.... Basically the fix which went into 2.4.7-pre7 moved where the process umask was applied to the creation mask to
/archives/xfs/2001-07/msg01201.html (9,467 bytes)

4. Re: umask fix (patch) (score: 1)
Author: xx>
Date: Thu, 26 Jul 2001 17:23:42 -0700 (PDT)
I think that nfsd should always run with a umask of 0, its umask should not depend on what umask was set in the sysadmins shell when it was launched. So nfsd should get its own fs context when it sta
/archives/xfs/2001-07/msg01207.html (8,630 bytes)

5. Re: umask fix (patch) (score: 1)
Author: xx>
Date: Fri, 27 Jul 2001 11:40:55 +1000
Hi there, So where did this application of the umask get moved to ? Can the acl default test be moved to the new point where the umask is applied ? This ACL code had to be added because we don't want
/archives/xfs/2001-07/msg01209.html (11,228 bytes)

6. Re: umask fix (patch) (score: 1)
Author: xx>
Date: Fri, 27 Jul 2001 07:14:48 -0500
Take a look at the callers of vfs_create and vfs_mknod in the current tree, when coming from local accesses the umask is only applied if there is no acl support in the filesystem, from NFS is is nev
/archives/xfs/2001-07/msg01215.html (10,602 bytes)

7. umask fix (patch) (score: 1)
Author: xxxxxx>
Date: Wed, 25 Jul 2001 19:24:17 -0700 (PDT)
The problem turned out to be in the nfsd code. The following fixes it: -- fs/nfsd/nfssvc.c 2001/05/29 19:53:13 1.13 +++ fs/nfsd/nfssvc.c 2001/07/26 02:27:26 @@ -150,6 +150,7 @@ MOD_INC_USE_COUNT; loc
/archives/xfs/2001-07/msg02456.html (7,220 bytes)

8. Re: umask fix (patch) (score: 1)
Author: xxxxxx>
Date: Thu, 26 Jul 2001 13:11:56 +1000
Kernel threads share the init task fs context. That change makes all future kernel threads run with umask 0, a big security exposure. This problem was supposed to have been fixed in 2.4.7-pre7.
/archives/xfs/2001-07/msg02457.html (7,950 bytes)

9. Re: umask fix (patch) (score: 1)
Author: xxxxxx>
Date: Thu, 26 Jul 2001 14:53:24 -0500
There is an XFS bug in here, I am not quite sure how to fix it at the moment though.... Basically the fix which went into 2.4.7-pre7 moved where the process umask was applied to the creation mask to
/archives/xfs/2001-07/msg02492.html (9,467 bytes)

10. Re: umask fix (patch) (score: 1)
Author: xxxxxx>
Date: Thu, 26 Jul 2001 17:23:42 -0700 (PDT)
I think that nfsd should always run with a umask of 0, its umask should not depend on what umask was set in the sysadmins shell when it was launched. So nfsd should get its own fs context when it sta
/archives/xfs/2001-07/msg02498.html (8,630 bytes)

11. Re: umask fix (patch) (score: 1)
Author: xxxxxx>
Date: Fri, 27 Jul 2001 11:40:55 +1000
Hi there, So where did this application of the umask get moved to ? Can the acl default test be moved to the new point where the umask is applied ? This ACL code had to be added because we don't want
/archives/xfs/2001-07/msg02500.html (11,228 bytes)

12. Re: umask fix (patch) (score: 1)
Author: xxxxxx>
Date: Fri, 27 Jul 2001 07:14:48 -0500
Take a look at the callers of vfs_create and vfs_mknod in the current tree, when coming from local accesses the umask is only applied if there is no acl support in the filesystem, from NFS is is nev
/archives/xfs/2001-07/msg02506.html (10,602 bytes)

13. umask fix (patch) (score: 1)
Author: Andrew Tridgell <tridge@xxxxxxxxxxx>
Date: Wed, 25 Jul 2001 19:24:17 -0700 (PDT)
The problem turned out to be in the nfsd code. The following fixes it: -- fs/nfsd/nfssvc.c 2001/05/29 19:53:13 1.13 +++ fs/nfsd/nfssvc.c 2001/07/26 02:27:26 @@ -150,6 +150,7 @@ MOD_INC_USE_COUNT; loc
/archives/xfs/2001-07/msg03747.html (7,220 bytes)

14. Re: umask fix (patch) (score: 1)
Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date: Thu, 26 Jul 2001 13:11:56 +1000
Kernel threads share the init task fs context. That change makes all future kernel threads run with umask 0, a big security exposure. This problem was supposed to have been fixed in 2.4.7-pre7.
/archives/xfs/2001-07/msg03748.html (7,981 bytes)

15. Re: umask fix (patch) (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Thu, 26 Jul 2001 14:53:24 -0500
There is an XFS bug in here, I am not quite sure how to fix it at the moment though.... Basically the fix which went into 2.4.7-pre7 moved where the process umask was applied to the creation mask to
/archives/xfs/2001-07/msg03783.html (9,529 bytes)

16. Re: umask fix (patch) (score: 1)
Author: Andrew Tridgell <tridge@xxxxxxxxxxx>
Date: Thu, 26 Jul 2001 17:23:42 -0700 (PDT)
I think that nfsd should always run with a umask of 0, its umask should not depend on what umask was set in the sysadmins shell when it was launched. So nfsd should get its own fs context when it sta
/archives/xfs/2001-07/msg03789.html (8,696 bytes)

17. Re: umask fix (patch) (score: 1)
Author: Timothy Shimmin <tes@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 27 Jul 2001 11:40:55 +1000
Hi there, So where did this application of the umask get moved to ? Can the acl default test be moved to the new point where the umask is applied ? This ACL code had to be added because we don't want
/archives/xfs/2001-07/msg03791.html (11,374 bytes)

18. Re: umask fix (patch) (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Fri, 27 Jul 2001 07:14:48 -0500
Take a look at the callers of vfs_create and vfs_mknod in the current tree, when coming from local accesses the umask is only applied if there is no acl support in the filesystem, from NFS is is nev
/archives/xfs/2001-07/msg03797.html (10,669 bytes)


This search system is powered by Namazu