From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] crypto: avoid leak of ctx when bad cipher mode is given
Date: Mon, 10 Jun 2024 13:50:05 +0200 [thread overview]
Message-ID: <d912659f-af55-48dd-961a-64ee40bbdfac@linaro.org> (raw)
In-Reply-To: <20240610094049.851127-2-berrange@redhat.com>
On 10/6/24 11:40, Daniel P. Berrangé wrote:
> This fixes Coverity CID-1546884
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> crypto/cipher-nettle.c.inc | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2024-06-10 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 9:40 [PATCH 0/2] crypto: two minor fixes Daniel P. Berrangé
2024-06-10 9:40 ` [PATCH 1/2] crypto: avoid leak of ctx when bad cipher mode is given Daniel P. Berrangé
2024-06-10 9:44 ` Peter Maydell
2024-06-10 11:50 ` Philippe Mathieu-Daudé [this message]
2024-06-10 13:43 ` Markus Armbruster
2024-06-10 9:40 ` [PATCH 2/2] crypto: use consistent error reporting pattern for unsupported cipher modes Daniel P. Berrangé
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=d912659f-af55-48dd-961a-64ee40bbdfac@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.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).