From: Chris Wright <chrisw@osdl.org>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Chris Wright <chrisw@osdl.org>,
"Serge E. Hallyn" <serue@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH] merge *_vm_enough_memory()s into a common helper
Date: Tue, 4 Jan 2005 14:26:58 -0800 [thread overview]
Message-ID: <20050104142658.Z2357@build.pdx.osdl.net> (raw)
In-Reply-To: <1104877039.20724.175.camel@moss-spartans.epoch.ncsc.mil>; from sds@epoch.ncsc.mil on Tue, Jan 04, 2005 at 05:17:19PM -0500
* Stephen Smalley (sds@epoch.ncsc.mil) wrote:
> On Tue, 2005-01-04 at 17:17, Chris Wright wrote:
> > * Serge E. Hallyn (serue@us.ibm.com) wrote:
> >
> > I'm fine with this with a few nits. Although I don't think it will apply
> > to current bk which has merge error in this area right now. Stephen,
> > are you ok with the way this one generates audit messages?
>
> Looks like the patch (with suggested fixes) will preserve the current
> behavior, i.e. no audit message generation for SELinux from the
> vm_enough_memory hook, while still auditing real uses of CAP_SYS_ADMIN
> elsewhere. That is what we want.
Good, thanks.
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-01-04 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 21:48 Serge E. Hallyn
2005-01-04 22:10 ` Stephen Smalley
2005-01-04 22:17 ` Chris Wright
2005-01-04 22:17 ` Stephen Smalley
2005-01-04 22:26 ` Chris Wright [this message]
2005-01-04 22:59 ` Nikita Danilov
2005-01-05 0:15 ` Alan Cox
2005-01-05 11:25 ` Christoph Hellwig
2005-01-05 13:17 ` Hugh Dickins
2005-01-05 16:30 ` Serge E. Hallyn
2005-01-05 19:24 ` Chris Wright
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=20050104142658.Z2357@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
--cc=serue@us.ibm.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®