mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Johansen <john.johansen@canonical.com>
To: jmorris@namei.org
Cc: linux-kernel@vger.kernel.org
Subject: [Patch 0/2] apparmor: fix issues with the 3.12 pull request
Date: Sun, 29 Sep 2013 08:39:20 -0700	[thread overview]
Message-ID: <1380469162-18604-1-git-send-email-john.johansen@canonical.com> (raw)

James,

could you pull and forward the follow fixes for the 3.12 kernel. Both
issues have had multiple reports.

thanks

---


The following changes since commit eb8948a03704f3dbbfc7e83090e20e93c6c476d2:

  X.509: remove possible code fragility: enumeration values not handled (2013-09-25 17:17:01 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor.git security-next

for you to fetch changes up to 94ecad0c9ca2c9345013d2417081cea7cf842c16:

  apparmor: fix suspicious RCU usage warning in policy.c/policy.h (2013-09-29 08:28:11 -0700)

----------------------------------------------------------------
John Johansen (1):
      apparmor: fix suspicious RCU usage warning in policy.c/policy.h

Tyler Hicks (1):
      apparmor: Use shash crypto API interface for profile hashes

 security/apparmor/crypto.c         | 34 ++++++++++++++++------------------
 security/apparmor/include/policy.h |  4 +++-
 security/apparmor/policy.c         |  3 ++-
 3 files changed, 21 insertions(+), 20 deletions(-)



             reply	other threads:[~2013-09-29 15:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-29 15:39 John Johansen [this message]
2013-09-29 15:39 ` [PATCH 1/2] apparmor: Use shash crypto API interface for profile hashes John Johansen
2013-09-29 15:39 ` [PATCH 2/2] apparmor: fix suspicious RCU usage warning in policy.c/policy.h John Johansen
2013-10-01  3:53   ` Paul E. McKenney

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=1380469162-18604-1-git-send-email-john.johansen@canonical.com \
    --to=john.johansen@canonical.com \
    --cc=jmorris@namei.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®