From: Eric Biggers <ebiggers@kernel.org>
To: keyrings@vger.kernel.org
Subject: Re: [PATCH] KEYS: asymmetric: return ENOMEM if akcipher_request_alloc() fails
Date: Thu, 10 Jan 2019 20:28:10 +0000 [thread overview]
Message-ID: <20190110202809.GB149637@gmail.com> (raw)
On Sat, Nov 03, 2018 at 10:41:07AM -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]")
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> crypto/asymmetric_keys/asym_tpm.c | 1 +
> crypto/asymmetric_keys/public_key.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/crypto/asymmetric_keys/asym_tpm.c b/crypto/asymmetric_keys/asym_tpm.c
> index 5d4c270463f60..8eeb2d251a82a 100644
> --- a/crypto/asymmetric_keys/asym_tpm.c
> +++ b/crypto/asymmetric_keys/asym_tpm.c
> @@ -479,6 +479,7 @@ static int tpm_key_encrypt(struct tpm_key *tk,
> if (ret < 0)
> goto error_free_tfm;
>
> + ret = -ENOMEM;
> req = akcipher_request_alloc(tfm, GFP_KERNEL);
> if (!req)
> goto error_free_tfm;
> diff --git a/crypto/asymmetric_keys/public_key.c b/crypto/asymmetric_keys/public_key.c
> index f5d85b47fcc6d..65fc08d9be087 100644
> --- a/crypto/asymmetric_keys/public_key.c
> +++ b/crypto/asymmetric_keys/public_key.c
> @@ -169,6 +169,7 @@ static int software_key_eds_op(struct kernel_pkey_params *params,
> if (IS_ERR(tfm))
> return PTR_ERR(tfm);
>
> + ret = -ENOMEM;
> req = akcipher_request_alloc(tfm, GFP_KERNEL);
> if (!req)
> goto error_free_tfm;
> --
> 2.19.1
>
Ping.
next reply other threads:[~2019-01-10 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 20:28 Eric Biggers [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-18 17:28 [PATCH] KEYS: asymmetric: return ENOMEM if akcipher_request_alloc() fails Eric Biggers
2019-02-07 23:36 Eric Biggers
2018-11-03 17:41 Eric Biggers
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=20190110202809.GB149637@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.