From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Andrew Morton <akpm@digeo.com>,
jmorris@intercode.com.au, lkml <linux-kernel@vger.kernel.org>,
lsm <linux-security-module@wirex.com>
Subject: Re: [RFC][PATCH] Security hook for vm_enough_memory
Date: 23 Jun 2003 17:40:25 +0100 [thread overview]
Message-ID: <1056386424.14228.78.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <1056385527.1709.415.camel@moss-huskers.epoch.ncsc.mil>
On Llu, 2003-06-23 at 17:25, Stephen Smalley wrote:
> This patch for 2.5.73 replaces the CAP_SYS_ADMIN test in
> vm_enough_memory with a security_vm_allocate hook call so that security
> modules such as SELinux can distinguish this test from other
> CAP_SYS_ADMIN checks. This change is necessary since the
> vm_enough_memory capability check is applied to all processes that
> allocate mappings and we don't want to spuriously audit CAP_SYS_ADMIN
> denials generated by this test. If anyone has any objections to this
> patch, please let me know. Thanks.
Is there any reason for not wrapping the entire vm_enough_memory() function
and using the current one as default. In some environments being able to make
total commit constraints based on roles may actually be useful.
(Think "sum of students memory < 40% of system" 8))
vm_enough_memory has to be kernel side but its basically policy so pluggable
IMHO is good.
next prev parent reply other threads:[~2003-06-23 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 16:25 Stephen Smalley
2003-06-23 16:40 ` Alan Cox [this message]
2003-06-23 19:04 ` Stephen Smalley
2003-06-24 13:42 ` Stephen Smalley
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=1056386424.14228.78.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@digeo.com \
--cc=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sds@epoch.ncsc.mil \
--cc=torvalds@transmeta.com \
/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®