From: Akhil Goyal <gakhil@marvell.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>,
"kai.ji@intel.com" <kai.ji@intel.com>,
"fanzhang.oss@gmail.com" <fanzhang.oss@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"feifei.wang2@arm.com" <feifei.wang2@arm.com>,
"nd@arm.com" <nd@arm.com>
Subject: RE: [EXT] [PATCH v2] crypto/openssl: fix warning on copy length
Date: Tue, 31 Jan 2023 08:09:21 +0000 [thread overview]
Message-ID: <CO6PR18MB4484B6483F6C3D5C21DB01DED8D09@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230109034021.2759215-1-ruifeng.wang@arm.com>
> When building with gcc 11.2.0, the compiler warns as follows:
> In function 'memcpy',
> inlined from 'openssl_set_session_auth_parameters' at
> ../drivers/crypto/openssl/rte_openssl_pmd.c:699:3,
> inlined from 'openssl_set_session_parameters' at
> ../drivers/crypto/openssl/rte_openssl_pmd.c:826:9:
> /usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning:
> '__builtin_memcpy' forming offset [4, 8] is out of the bounds [0, 4] [-Warray-
> bounds]
>
> Fixed the warning by copying up to string / buffer size.
>
> Fixes: 75adf1eae44f ("crypto/openssl: update HMAC routine with 3.0 EVP API")
> Cc: stable@dpdk.org
> Cc: kai.ji@intel.com
>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Feifei Wang <feifei.wang2@arm.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2023-01-31 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 10:15 [PATCH] " Ruifeng Wang
2023-01-06 10:26 ` David Marchand
2023-01-09 3:31 ` Ruifeng Wang
2023-01-09 3:40 ` [PATCH v2] " Ruifeng Wang
2023-01-31 8:09 ` Akhil Goyal [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=CO6PR18MB4484B6483F6C3D5C21DB01DED8D09@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=feifei.wang2@arm.com \
--cc=kai.ji@intel.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.com \
--cc=stable@dpdk.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).