mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org
Cc: dhowells@redhat.com, sgallagh@redhat.com, rdunlap@infradead.org,
	keyrings@linux-nfs.org, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, simo@redhat.com
Subject: [GIT PULL] KEYS: More fixes for next branch
Date: Thu, 14 Nov 2013 18:57:57 +0000	[thread overview]
Message-ID: <9945.1384455477@warthog.procyon.org.uk> (raw)


Hi James,

Here are some fixes that are needed for the keyrings stuff in your next
branch.  Could you pull them please?

David
---
The following changes since commit 217091dd7a7a1bdac027ddb7c5a25f6ac0b8e241:

  ima: define '_ima' as a builtin 'trusted' keyring (2013-10-31 20:20:48 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git keys-devel

for you to fetch changes up to 62fe318256befbd1b4a6765e71d9c997f768fe79:

  KEYS: Fix keyring content gc scanner (2013-11-14 14:09:53 +0000)

----------------------------------------------------------------
(from the branch description for keys-devel local branch)

Keyrings development
----------------------------------------------------------------
David Howells (4):
      KEYS: The RSA public key algorithm needs to select MPILIB
      KEYS: Fix UID check in keyctl_get_persistent()
      KEYS: Fix error handling in big_key instantiation
      KEYS: Fix keyring content gc scanner

 crypto/asymmetric_keys/Kconfig |  1 +
 security/keys/big_key.c        |  1 +
 security/keys/gc.c             | 42 +--------------------------------------
 security/keys/keyring.c        | 45 ++++++++++++++++++++++++++++++++----------
 security/keys/persistent.c     |  6 ++----
 5 files changed, 40 insertions(+), 55 deletions(-)

             reply	other threads:[~2013-11-14 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 18:57 David Howells [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-06 15:25 David Howells

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=9945.1384455477@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sgallagh@redhat.com \
    --cc=simo@redhat.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®