From: Akhil Goyal <gakhil@marvell.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Ashwin Sekhar T K <asekhar@marvell.com>,
Kai Ji <kai.ji@intel.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH] crypto/openssl: fix potential string overflow
Date: Wed, 6 Nov 2024 11:32:48 +0000 [thread overview]
Message-ID: <CO6PR18MB4484AF7717B5C7D9FA466EC8D8532@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20241017160754.132762-1-stephen@networkplumber.org>
> The algorithm name is a string and should be copied with strlcpy()
> rather than rte_memcpy(). This fixes a warning detected with
> clang and ASAN.
>
> Bugzilla ID: 1565
> Fixes: 2b9c693f6ef5 ("crypto/openssl: support AES-CMAC operations")
> Cc: asekhar@marvell.com
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Cc: stable@dpdk.org
Applied to dpdk-next-crypto
Thanks.
parent reply other threads:[~2024-11-06 11:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20241017160754.132762-1-stephen@networkplumber.org>]
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=CO6PR18MB4484AF7717B5C7D9FA466EC8D8532@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=asekhar@marvell.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).