From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: keyrings@linux-nfs.org, linux-nfs@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Keyrings] [GIT PULL] Keyrings (& NFS) fixes
Date: Tue, 2 Dec 2014 09:49:04 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.11.1412020947060.18348@namei.org> (raw)
In-Reply-To: <12126.1417429021@warthog.procyon.org.uk>
On Mon, 1 Dec 2014, David Howells wrote:
> 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 a6aacbde406eeb6f8fc218b2c6172825f5e73fcf:
>
> Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity into next (2014-11-19 21:36:07 +1100)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-fixes-20141121
>
Because these patches are going to current Linus, you need to apply these
patches to a tree based on his tree, and send a pull req to me for that.
--
James Morris
<jmorris@namei.org>
_______________________________________________
Keyrings mailing list
Keyrings@linux-nfs.org
To change your subscription to this list, please see http://linux-nfs.org/cgi-bin/mailman/listinfo/keyrings
prev parent reply other threads:[~2014-12-01 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 10:17 [GIT PULL] Keyrings (& NFS) fixes David Howells
2014-12-01 22:49 ` James Morris [this message]
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=alpine.LRH.2.11.1412020947060.18348@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--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