From: Anoob Joseph <anoobj@marvell.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Akhil Goyal <gakhil@marvell.com>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
"daxuex.gao@intel.com" <daxuex.gao@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] [PATCH v2] test/crypto: fix warnings for optimization=1 build
Date: Mon, 13 Jun 2022 09:54:14 +0000 [thread overview]
Message-ID: <PH0PR18MB4672011985A1029217BBEB8CDFAB9@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <611b8127523b793a6fde85213c6493aacca8dc16.1655112181.git.rahul.lakkireddy@chelsio.com>
> Fail IPSec ESN and antireplay cases, if there are no packets. Fixes following
> warning when using optimization=1 build flag with GCC 11.
>
> ../app/test/test_cryptodev.c: In function ‘test_ipsec_pkt_replay’:
> ../app/test/test_cryptodev.c:10074:15: warning: ‘td_outb’ may be used
> uninitialized [-Wmaybe-uninitialized]
> ret = test_ipsec_proto_process(td_outb, td_inb, nb_pkts, true,
>
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> &flags);
> ~~~~~~~
> ../app/test/test_cryptodev.c:9150:1: note: by argument 1 of type ‘const
> struct ipsec_test_data[]’ to ‘test_ipsec_proto_process’ declared here
> test_ipsec_proto_process(const struct ipsec_test_data td[],
> ^~~~~~~~~~~~~~~~~~~~~~~~
> ../app/test/test_cryptodev.c:10056:32: note: ‘td_outb’ declared here
> struct ipsec_test_data td_outb[IPSEC_TEST_PACKETS_MAX];
> ^~~~~~~
>
> Bugzilla ID: 1032
> Fixes: d02c6bfcb99a ("test/crypto: add ESN and antireplay cases")
> Cc: stable@dpdk.org
>
> Reported-by: Daxue Gao <daxuex.gao@intel.com>
> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Acked-by: Anoob Joseph <anoobj@marvell.com>
next prev parent reply other threads:[~2022-06-13 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 22:09 [PATCH] " Rahul Lakkireddy
2022-06-13 5:02 ` [EXT] " Anoob Joseph
2022-06-13 9:52 ` [PATCH v2] " Rahul Lakkireddy
2022-06-13 9:54 ` Anoob Joseph [this message]
2022-06-15 15:08 ` [EXT] " Akhil Goyal
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=PH0PR18MB4672011985A1029217BBEB8CDFAB9@PH0PR18MB4672.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=daxuex.gao@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=roy.fan.zhang@intel.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).