From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm1
Date: Mon, 10 May 2004 22:37:55 +0100 [thread overview]
Message-ID: <20040510223755.A7773@infradead.org> (raw)
In-Reply-To: <20040510024506.1a9023b6.akpm@osdl.org>; from akpm@osdl.org on Mon, May 10, 2004 at 02:45:06AM -0700
> +hugetlb_shm_group-sysctl-patch.patch
>
> Add /proc/sys/vm/hugetlb_shm_group: this holds the group ID of users who may
> allocate hugetlb shm segments without CAP_IPC_LOCK. For Oracle.
>
> +mlock_group-sysctl.patch
>
> /proc/sys/vm/mlock_group: group ID of users who can do mlock() without
> CAP_IPC_LOCK. Not sure that we need this.
These two just introduced a subtile behaviour change during stable series,
possibly (not likely) leading to DoS opportunities from applications running
as gid 0. Really, with capabilities first and now selinux we have moved
away from treating uid 0 special, so introducing special casing of a gid
now is more than just braindead.
next prev parent reply other threads:[~2004-05-10 21:37 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 9:45 2.6.6-mm1 Andrew Morton
2004-05-10 10:52 ` 2.6.6-mm1 Dominik Karall
2004-05-10 11:18 ` 2.6.6-mm1 Dave Jones
2004-05-10 12:20 ` 2.6.6-mm1 Nick Piggin
2004-05-10 12:22 ` 2.6.6-mm1 Dave Jones
2004-05-10 12:35 ` 2.6.6-mm1: FB_ASILIANT: no help text Adrian Bunk
2004-05-10 12:45 ` 2.6.6-mm1: a different CONFIG_STANDALONE approach Adrian Bunk
2004-05-10 12:57 ` Adrian Bunk
2004-05-10 20:00 ` Andrew Morton
2004-05-10 14:38 ` 2.6.6-mm1 Norberto Bensa
2004-05-10 14:55 ` 2.6.6-mm1 Dominik Karall
2004-05-10 15:02 ` 2.6.6-mm1 Norberto Bensa
2004-05-10 15:22 ` 2.6.6-mm1 Dominik Karall
2004-05-10 15:33 ` 2.6.6-mm1 Norberto Bensa
2004-05-10 15:20 ` 2.6.6-mm1 Christoph Hellwig
2004-05-11 5:21 ` 2.6.6-mm1 Andrew Morton
2004-05-10 21:37 ` Christoph Hellwig [this message]
2004-05-10 22:02 ` 2.6.6-mm1 Andrew Morton
2004-05-10 22:05 ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 22:15 ` 2.6.6-mm1 Andrew Morton
2004-05-10 22:20 ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 22:47 ` 2.6.6-mm1 Andrew Morton
2004-05-10 22:48 ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 23:16 ` 2.6.6-mm1 Matt Mackall
2004-05-10 22:27 ` 2.6.6-mm1 Valdis.Kletnieks
2004-05-10 22:48 ` 2.6.6-mm1 Andrew Morton
2004-05-10 23:01 ` 2.6.6-mm1 Valdis.Kletnieks
2004-05-10 23:11 ` 2.6.6-mm1 Chris Wedgwood
2004-05-10 23:14 ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 23:28 ` 2.6.6-mm1 Andrew Morton
2004-05-10 23:33 ` 2.6.6-mm1 Chris Wedgwood
2004-05-10 23:51 ` 2.6.6-mm1 Andrew Morton
2004-05-10 23:53 ` 2.6.6-mm1 Chris Wedgwood
2004-05-11 0:14 ` 2.6.6-mm1 Andrew Morton
2004-05-11 0:24 ` 2.6.6-mm1 Wim Coekaerts
2004-05-11 1:10 ` 2.6.6-mm1 Andrew Morton
2004-05-11 1:51 ` 2.6.6-mm1 Wim Coekaerts
2004-05-11 6:23 ` 2.6.6-mm1 Christoph Hellwig
2004-05-12 2:44 ` 2.6.6-mm1 Andrea Arcangeli
2004-05-12 5:11 ` 2.6.6-mm1 Chris Wedgwood
2004-05-11 15:12 ` 2.6.6-mm1 Wim Coekaerts
2004-05-12 5:42 ` 2.6.6-mm1 Christoph Hellwig
2004-05-12 5:50 ` 2.6.6-mm1 Christoph Hellwig
2004-05-11 6:22 ` 2.6.6-mm1 Christoph Hellwig
2004-05-11 6:21 ` 2.6.6-mm1 Christoph Hellwig
2004-05-11 6:37 ` 2.6.6-mm1 William Lee Irwin III
2004-05-11 6:18 ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 23:33 ` 2.6.6-mm1 Chris Wright
2004-05-11 1:59 ` 2.6.6-mm1 Matt Mackall
2004-05-11 14:34 ` 2.6.6-mm1 Stephen Smalley
2004-05-11 16:48 ` 2.6.6-mm1 Chris Wright
2004-05-12 12:49 ` 2.6.6-mm1 Sean Neakums
2004-05-12 19:26 ` 2.6.6-mm1 Andrew Morton
2004-05-10 12:43 2.6.6-mm1 Sid Boyce
2004-05-12 8:13 ` 2.6.6-mm1 Andrew Morton
2004-05-10 16:50 2.6.6-mm1 Sid Boyce
[not found] <fa.j4d62qo.1144tpk@ifi.uio.no>
[not found] ` <fa.gg699ad.b2omr9@ifi.uio.no>
2004-05-11 6:33 ` 2.6.6-mm1 Andy Lutomirski
2004-05-11 10:34 2.6.6-mm1 Sid Boyce
2004-05-11 14:49 2.6.6-mm1 Neil Schemenauer
2004-05-11 18:55 ` 2.6.6-mm1 Andrew Morton
2004-05-12 12:26 2.6.6-mm1 Sid Boyce
2004-05-12 15:27 2.6.6-mm1 Sid Boyce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040510223755.A7773@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®