From: Eric Biggers <ebiggers@kernel.org>
To: keyrings@vger.kernel.org
Subject: Re: [PATCH RESEND] KEYS: asymmetric: return ENOMEM if akcipher_request_alloc() fails
Date: Mon, 09 Dec 2019 20:19:20 +0000 [thread overview]
Message-ID: <20191209201920.GE149190@gmail.com> (raw)
In-Reply-To: <20190529210132.120114-1-ebiggers@kernel.org>
On Tue, Nov 12, 2019 at 10:09:08PM +0200, Jarkko Sakkinen wrote:
> On Mon, Nov 11, 2019 at 10:20:55AM -0800, Eric Biggers wrote:
> > On Mon, Oct 14, 2019 at 10:48:46PM +0300, Jarkko Sakkinen wrote:
> > > On Wed, Oct 09, 2019 at 04:03:49PM -0700, Eric Biggers wrote:
> > > > From: Eric Biggers <ebiggers@google.com>
> > > >
> > > > No error code was being set on this error path.
> > > >
> > > > Fixes: ad4b1eb5fb33 ("KEYS: asym_tpm: Implement encryption operation [ver #2]")
> > > > Fixes: c08fed737126 ("KEYS: Implement encrypt, decrypt and sign for software asymmetric key [ver #2]")
> > > > Reviewed-by: James Morris <jamorris@linux.microsoft.com>
> > > > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > >
> > > Cc: stable@vger.kernel.org
> > > Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > >
> > > I can pick this up to my tree given the TPM association. David?
> > >
> > > /Jarkko
> >
> > Ping.
>
> I can pick this up to my v5.5-rc2 PR (already sent one for rc1).
>
> /Jarkko
Ping.
next prev parent reply other threads:[~2019-12-09 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 21:01 [PATCH RESEND] KEYS: asymmetric: return ENOMEM if akcipher_request_alloc() fails Eric Biggers
2019-05-29 21:48 ` James Morris
2019-08-22 15:35 ` Eric Biggers
2019-10-09 23:03 ` Eric Biggers
2019-10-14 19:48 ` Jarkko Sakkinen
2019-11-11 18:20 ` Eric Biggers
2019-11-12 20:09 ` Jarkko Sakkinen
2019-12-09 20:19 ` Eric Biggers [this message]
2019-12-12 21:46 ` Jarkko Sakkinen
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=20191209201920.GE149190@gmail.com \
--to=ebiggers@kernel.org \
--cc=keyrings@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.