From: Akhil Goyal <akhil.goyal@nxp.com>
To: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"mdr@ashroe.eu" <mdr@ashroe.eu>,
"anoobj@marvell.com" <anoobj@marvell.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"david.coyle@intel.com" <david.coyle@intel.com>,
"radu.nicolau@intel.com" <radu.nicolau@intel.com>
Subject: Re: [dpdk-dev] [PATCH] security: update session create API
Date: Sat, 10 Oct 2020 22:09:33 +0000 [thread overview]
Message-ID: <VI1PR04MB31681D02A8C14B98C976D19EE6090@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <a1c1aae0-0602-0f08-37d6-6bbc8478ab81@partner.samsung.com>
Hi Lukasz,
Thanks for the review.
> > diff --git a/app/test/test_security.c b/app/test/test_security.c
> > index 77fd5adc6..ed7de348f 100644
> > --- a/app/test/test_security.c
> > +++ b/app/test/test_security.c
> > @@ -237,6 +237,7 @@ static struct mock_session_create_data {
> > struct rte_security_session_conf *conf;
> > struct rte_security_session *sess;
> > struct rte_mempool *mp;
> > + struct rte_mempool *priv_mp;
> >
> > int ret;
> >
> session_create op is now called with private mbuf, so you need also to
> update assert in mock session_create:
OK will be fixed in v2
>
> @@ -248,13 +249,13 @@ static int
> mock_session_create(void *device,
> struct rte_security_session_conf *conf,
> struct rte_security_session *sess,
> - struct rte_mempool *mp)
> + struct rte_mempool *priv_mp)
> {
> mock_session_create_exp.called++;
>
> MOCK_TEST_ASSERT_POINTER_PARAMETER(mock_session_create_exp,
> device);
> MOCK_TEST_ASSERT_POINTER_PARAMETER(mock_session_create_exp,
> conf);
> - MOCK_TEST_ASSERT_POINTER_PARAMETER(mock_session_create_exp,
> mp);
> + MOCK_TEST_ASSERT_POINTER_PARAMETER(mock_session_create_exp,
> priv_mp);
>
> mock_session_create_exp.sess = sess;
>
>
>
> > @@ -502,6 +503,7 @@ struct rte_security_ops mock_ops = {
> > */
> > static struct security_testsuite_params {
> > struct rte_mempool *session_mpool;
> > + struct rte_mempool *session_priv_mpool;
> > } testsuite_params = { NULL };
> >
> > /**
> > @@ -525,6 +527,7 @@ static struct security_unittest_params {
> > };
> >
> > #define SECURITY_TEST_MEMPOOL_NAME "SecurityTestsMempoolName"
> > +#define SECURITY_TEST_PRIV_MEMPOOL_NAME
> "SecurityTestsPrivMempoolName"
> Please make the mempool name shorter, otherwise it causes tests to fail:
>
> EAL: Test assert testsuite_setup line 558 failed: Cannot create priv
> mempool File name too long
>
Fixed in v2
> > #define SECURITY_TEST_MEMPOOL_SIZE 15
> > #define SECURITY_TEST_SESSION_OBJECT_SIZE sizeof(struct
> rte_security_session)
> >
> > @@ -545,6 +548,17 @@ testsuite_setup(void)
> > SOCKET_ID_ANY, 0);
> > TEST_ASSERT_NOT_NULL(ts_params->session_mpool,
> > "Cannot create mempool %s\n",
> rte_strerror(rte_errno));
> > +
> > + ts_params->session_priv_mpool = rte_mempool_create(
> > + SECURITY_TEST_PRIV_MEMPOOL_NAME,
> > + SECURITY_TEST_MEMPOOL_SIZE,
> > + rte_security_session_get_size(&unittest_params.ctx),
> > + 0, 0, NULL, NULL, NULL, NULL,
> > + SOCKET_ID_ANY, 0);
> > + TEST_ASSERT_NOT_NULL(ts_params->session_priv_mpool,
> > + "Cannot create priv mempool %s\n",
> > + rte_strerror(rte_errno));
> > +
> If creation of private data mpool fails, primary mempool need to be
> freed before function returns failure code.
This is an issue in whole of the file.
However, have fixed it in v2 for this particular case in v2.
next prev parent reply other threads:[~2020-10-10 22:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200903201022eucas1p19a5154b9fb7063f72b18dea1114eeed3@eucas1p1.samsung.com>
2020-09-03 20:09 ` akhil.goyal
2020-09-04 16:04 ` Lukasz Wojciechowski
2020-10-10 22:09 ` Akhil Goyal [this message]
2020-09-24 16:22 ` Coyle, David
2020-10-10 22:06 ` Akhil Goyal
2020-10-10 22:11 ` [dpdk-dev] [PATCH v2] " Akhil Goyal
2020-10-12 17:46 ` Akhil Goyal
2020-10-13 2:12 ` Lukasz Wojciechowski
2020-10-14 19:00 ` Akhil Goyal
2020-10-15 1:14 ` Lukasz Wojciechowski
2020-10-14 18:56 ` [dpdk-dev] [PATCH v3] " Akhil Goyal
2020-10-15 1:11 ` Lukasz Wojciechowski
2020-10-17 11:50 ` [dpdk-dev] [PATCH v4] " Akhil Goyal
2020-10-17 13:13 ` Lukasz Wojciechowski
2020-10-18 8:47 ` Akhil Goyal
2020-10-18 9:30 ` Lukasz Wojciechowski
2020-10-18 9:37 ` Lukasz Wojciechowski
2020-10-18 9:42 ` Akhil Goyal
2020-10-18 9:40 ` [dpdk-dev] [PATCH v5] " Akhil Goyal
2020-10-18 11:03 ` Lukasz Wojciechowski
2020-10-19 7:51 ` Thomas Monjalon
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=VI1PR04MB31681D02A8C14B98C976D19EE6090@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=david.coyle@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=konstantin.ananyev@intel.com \
--cc=l.wojciechow@partner.samsung.com \
--cc=mdr@ashroe.eu \
--cc=radu.nicolau@intel.com \
--cc=thomas@monjalon.net \
/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).