public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: [PULL] Smack: please pull for security-testing next
Date: Wed, 09 Feb 2011 21:38:34 -0800	[thread overview]
Message-ID: <4D5379DA.2020109@schaufler-ca.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1102100852180.18248@tundra.namei.org>

The following changes since commit 0e0a070d3a47d279de66e08244769556deae2eee:
  Casey Schaufler (1):
        Smack: correct behavior in the mmap hook

are available in the git repository at:

  git://gitorious.org/smack-next/kernel.git next

Casey Schaufler (1):
      Smack: correct final mmap check comparison

Shan Wei (1):
      security:smack: kill unused SMACK_LIST_MAX, MAY_ANY and MAY_ANYWRITE

 security/smack/smack.h     |    8 --------
 security/smack/smack_lsm.c |    2 +-
 2 files changed, 1 insertions(+), 9 deletions(-)

  parent reply	other threads:[~2011-02-10  5:38 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
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         ` Casey Schaufler [this message]
2011-02-10  8:01           ` [PULL] Smack: please pull for security-testing next 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=4D5379DA.2020109@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox