From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org
Cc: dhowells@redhat.com, linux-nfs@vger.kernel.org,
linux-security-module@vger.kernel.org, keyrings@linux-nfs.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Keyrings (& NFS) fixes
Date: Mon, 01 Dec 2014 23:16:44 +0000 [thread overview]
Message-ID: <5000.1417475804@warthog.procyon.org.uk> (raw)
Hi James,
Can you pass these patches on to Linus please?
The first one fixes the handling of maximum buffer size for key descriptions,
fixing the size at 4095 + NUL char rather than whatever PAGE_SIZE happens to
be and permits you to read back the full description without it getting
clipped because some extra information got prepended.
The second and third fix a bug in NFS idmapper handling whereby a key
representing a mapping between an id and a name expires and causing
EKEYEXPIRED to be seen internally in NFS (which prevents the mapping from
happening) rather than re-looking up the mapping.
Thanks,
David
---
The following changes since commit 009d0431c3914de64666bec0d350e54fdd59df6a:
Linux 3.18-rc7 (2014-11-30 16:42:27 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-fixes-20141201
for you to fetch changes up to 0b0a84154eff56913e91df29de5c3a03a0029e38:
KEYS: request_key() should reget expired keys rather than give EKEYEXPIRED (2014-12-01 22:52:53 +0000)
----------------------------------------------------------------
(from the branch description for keys-fixes local branch)
Keyrings fixes
Keyrings fixes
----------------------------------------------------------------
David Howells (3):
KEYS: Fix the size of the key description passed to/from userspace
KEYS: Simplify KEYRING_SEARCH_{NO,DO}_STATE_CHECK flags
KEYS: request_key() should reget expired keys rather than give EKEYEXPIRED
security/keys/internal.h | 1 +
security/keys/keyctl.c | 56 +++++++++++++++++++---------------------
security/keys/keyring.c | 10 ++++---
security/keys/request_key.c | 2 ++
security/keys/request_key_auth.c | 1 +
5 files changed, 36 insertions(+), 34 deletions(-)
next reply other threads:[~2014-12-01 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 23:16 David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-01 10:17 [GIT PULL] Keyrings (& NFS) fixes David Howells
2014-12-01 22:49 ` James Morris
2014-11-21 21:53 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=5000.1417475804@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-nfs@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;
as well as URLs for NNTP newsgroup(s).