Messages in this thread | | | Date | Mon, 10 May 2004 15:48:00 -0700 | From | Andrew Morton <> | Subject | Re: 2.6.6-mm1 |
| |
Valdis.Kletnieks@vt.edu wrote: > > On Mon, 10 May 2004 15:02:03 PDT, Andrew Morton said: > > > > These two just introduced a subtile behaviour change during stable series, > > > possibly (not likely) leading to DoS opportunities from applications running > > > as gid 0. > > > > mlock_group is likely to go away. > > > > Is an unprivileged user likely to have gid 0? Easy enough to fix, anyway. > > Equally important, is gid 0 (with its other possible overloadings) something that we > want to put on a user just because they have a need for mlock??
You misread the code. The sysctl, when non-zero, specifies the group which is allowed to allocate hugetlb-backed shm segments. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |