From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 1/2] crypto: fix uninitialized variable coverity warning
Date: Tue, 27 Feb 2024 16:03:16 -0600 [thread overview]
Message-ID: <e764060c-8289-4c6f-88e2-73457a7629b5@gmail.com> (raw)
In-Reply-To: <20240227211618.318442-1-prestwoj@gmail.com>
Hi James,
On 2/27/24 15:16, James Prestwood wrote:
> Same as for aes_siv_decrypt, check num_ads before calling memcpy.
> ---
> src/crypto.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Both applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2024-02-27 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 21:16 [PATCH 1/2] crypto: fix uninitialized variable coverity warning James Prestwood
2024-02-27 21:16 ` [PATCH 2/2] station: warn on missing scan_bss in station_transition_start James Prestwood
2024-02-27 22:03 ` Denis Kenzior [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=e764060c-8289-4c6f-88e2-73457a7629b5@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).