From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, "Jiang, YuX" <yux.jiang@intel.com>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>
Subject: RE: [PATCH v2] test/ipsec: fix performance test failure
Date: Thu, 23 Jun 2022 11:18:00 +0000 [thread overview]
Message-ID: <BYAPR11MB27111E5384282423FB646AD8FEB59@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220621133046.2827485-1-vladimir.medvedkin@intel.com>
> -----Original Message-----
> From: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> Sent: Tuesday, June 21, 2022 9:31 PM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; stable@dpdk.org; Konstantin Ananyev
> <konstantin.v.ananyev@yandex.ru>; Iremonger, Bernard
> <bernard.iremonger@intel.com>
> Subject: [PATCH v2] test/ipsec: fix performance test failure
>
> This patch initializes with 0 rte_ipsec_sa_prm inside the ipsec_sa struct.
> Before it was passed uninitialized to rte_ipsec_sa_init(), which does not
> check whether prm->ipsec_xform.esn.value is greater than sa->sqn_mask.
>
> Bugzilla ID: 1023
> Fixes: f7f3ac6dcbe2 ("test/ipsec: add performance cases")
> Cc: stable@dpdk.org
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> ---
>
> Notes:
> v2:
> - fix gcc4 warnings
>
> app/test/test_ipsec_perf.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/app/test/test_ipsec_perf.c b/app/test/test_ipsec_perf.c index
> 346a851648..11de9a6aac 100644
> --- a/app/test/test_ipsec_perf.c
> +++ b/app/test/test_ipsec_perf.c
> @@ -592,8 +592,8 @@ testsuite_teardown(void) static int
> test_libipsec_perf(void)
> {
> - struct ipsec_sa sa_out;
> - struct ipsec_sa sa_in;
> + struct ipsec_sa sa_out = { .sa_prm = { 0 } };
> + struct ipsec_sa sa_in = { .sa_prm = { 0 } };
> uint32_t i;
> int ret;
>
> --
> 2.25.1
Tested-by: Yu Jiang <YuX.Jiang@intel.com>
prev parent reply other threads:[~2022-06-23 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 17:18 [PATCH] " Vladimir Medvedkin
2022-06-21 11:08 ` [EXT] " Akhil Goyal
2022-06-21 13:30 ` [PATCH v2] " Vladimir Medvedkin
2022-06-21 17:23 ` [EXT] " Akhil Goyal
2022-06-23 11:18 ` Jiang, YuX [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=BYAPR11MB27111E5384282423FB646AD8FEB59@BYAPR11MB2711.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@intel.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 NNTP newsgroup(s).