From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org
Cc: dhowells@redhat.com, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org, gang.chen@asianux.com,
yongjun_wei@trendmicro.com.cn, sgallagh@redhat.com,
jwboyer@fedoraproject.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] KEYS: Fixes for next branch
Date: Wed, 30 Oct 2013 13:08:40 +0000 [thread overview]
Message-ID: <30717.1383138520@warthog.procyon.org.uk> (raw)
Hi James,
Could you pull these five commits into your next branch? They are a set of
fixes, some for the commits you have there and some for the upstream kernel.
David
---
The following changes since commit 50b719f811583a47762ecb7e480d253abc2eb22f:
Merge branch 'smack-for-3.13' of git://git.gitorious.org/smack-next/kernel into ra-next (2013-10-30 14:07:10 +1100)
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 6ef4d2eaf5a46d4ab6db02612b5e883b834017b8:
kernel/system_certificate.S: use real contents instead of macro GLOBAL() (2013-10-30 12:58:00 +0000)
----------------------------------------------------------------
(from the branch description for keys-devel local branch)
clone of "master"
----------------------------------------------------------------
Chen Gang (1):
kernel/system_certificate.S: use real contents instead of macro GLOBAL()
David Howells (2):
KEYS: Fix a race between negating a key and reading the error set
KEYS: Fix keyring quota misaccounting on key replacement and unlink
Josh Boyer (1):
KEYS: Make BIG_KEYS boolean
Wei Yongjun (1):
KEYS: fix error return code in big_key_instantiate()
kernel/system_certificates.S | 10 ++++------
security/keys/Kconfig | 2 +-
security/keys/big_key.c | 4 +++-
security/keys/key.c | 3 ++-
security/keys/keyring.c | 28 ++++++++++++++++------------
security/keys/request_key.c | 4 +++-
6 files changed, 29 insertions(+), 22 deletions(-)
next reply other threads:[~2013-10-30 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 13:08 David Howells [this message]
2013-10-30 22:45 ` 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=30717.1383138520@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=gang.chen@asianux.com \
--cc=jmorris@namei.org \
--cc=jwboyer@fedoraproject.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sgallagh@redhat.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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®