From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>
Cc: LKLM <linux-kernel@vger.kernel.org>,
LSM <linux-security-module@vger.kernel.org>,
"Sakkinen Jarkko.2 \(EXT-Tieto/Tampere\)"
<ext-jarkko.2.sakkinen@nokia.com>,
Janne Karhunen <Janne.Karhunen@nokia.com>,
"Reshetova Elena \(Nokia-D/Helsinki\)"
<elena.reshetova@nokia.com>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: Subject: [PATCH] Smack: mmap controls for library containment
Date: Wed, 09 Feb 2011 05:15:22 -0800 [thread overview]
Message-ID: <4D52936A.6010407@schaufler-ca.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1102091851030.12310@tundra.namei.org>
On 2/8/2011 11:51 PM, James Morris wrote:
> On Tue, 8 Feb 2011, Casey Schaufler wrote:
>
> Subject: [PATCH] Smack: correct behavior in the mmap hook
>
> The mmap policy enforcement was not properly handling the
> interaction between the global and local rule lists.
> Instead of going through one and then the other, which
> missed the important case where a rule specified that
> there should be no access, combine the access limitations
> where there is a rule in each list.
>
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> Applied to
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next
>
James, I made an error and failed to say that this and Shan Wei's clean-up
should be pulled from git://gitorious.org/smack-next/kernel.git
next prev parent reply other threads:[~2011-02-09 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 16:21 Subject: [PATCH] Smack: mmap controls for library containment Casey Schaufler
2011-01-17 22:56 ` James Morris
2011-02-09 0:36 ` Casey Schaufler
2011-02-09 7:51 ` James Morris
2011-02-09 13:15 ` Casey Schaufler [this message]
2011-02-09 21:53 ` James Morris
2011-02-09 23:45 ` Casey Schaufler
2011-02-10 0:00 ` James Morris
2011-02-10 5:38 ` [PULL] Smack: please pull for security-testing next Casey Schaufler
2011-02-10 8:01 ` James Morris
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=4D52936A.6010407@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=Janne.Karhunen@nokia.com \
--cc=elena.reshetova@nokia.com \
--cc=ext-jarkko.2.sakkinen@nokia.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.