From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: Garry Marshall <gazmarsh@meaningfulname.net>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"vladimir.medvedkin@intel.com" <vladimir.medvedkin@intel.com>
Subject: RE: [PATCH] ipsec: use sym_session_opaque_data for RTE_SECURITY_TYPE_CPU_CRYPTO
Date: Tue, 31 Oct 2023 17:53:30 +0000 [thread overview]
Message-ID: <de293a0aedd0408f9ea7dc8b733a4961@huawei.com> (raw)
In-Reply-To: <CAEZ1fRDuyMx2HoEtZhyMHrzKZOcze=DXWw3grAqnAyc+qBxRDA@mail.gmail.com>
Hi Garry,
> Hi Konstantin, Akhil,
>
> The patch is based on an issue I encountered when using the CPU_CRYPTO
> support - I was having problems where the ipsec session lookup was
> failing / was inconsistent.
>
> Examining the code in DPDK and looking for the use of
> RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO I could see a reasonably
> consistent pattern where if TYPE_NONE or TYPE_CPU_CRYPTO was set -
> then the code was making use of ss->crypto.ses instead of
> ss->security.ses.
>
> For example - see examples/ipsec-secgw.c where the one_session_free
> function has the following code:
>
> if (ips->type == RTE_SECURITY_ACTION_TYPE_NONE ||
> ips->type == RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO) {
> /* Session has not been created */
> if (ips->crypto.ses == NULL)
> return 0;
>
> ret = rte_cryptodev_sym_session_free(ips->crypto.dev_id,
> ips->crypto.ses);
> } else {
> /* Session has not been created */
> if (ips->security.ctx == NULL || ips->security.ses == NULL)
> return 0;
>
> ret = rte_security_session_destroy(ips->security.ctx,
> ips->security.ses);
> }
>
> And similarly - if we look at the session_check function in lib/ipsec/ses.c:
>
> if (ss->type == RTE_SECURITY_ACTION_TYPE_NONE ||
> ss->type == RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO) {
> if (ss->crypto.ses == NULL)
> return -EINVAL;
> } else {
> if (ss->security.ses == NULL)
> return -EINVAL;
> if ((ss->type == RTE_SECURITY_ACTION_TYPE_INLINE_CRYPTO ||
> ss->type ==
> RTE_SECURITY_ACTION_TYPE_INLINE_PROTOCOL) &&
> ss->security.ctx == NULL)
> return -EINVAL;
> }
Thanks for explanation.
Yes, I agree that TYPE_NONE and TYPE_CPU_CRYPTO both use crypto session
to keep/propagate crypto related pamaters.
What is not clear to me why for and TYPE_CPU_CRYPTO we need to store
pointer to rte_ipsec_session as opaque user data for crypto session.
As I remember, for lookaside crypto we need to do that to extract
related rte_ipsec_session pointer from crypto_op, after lookaside crypto device
finished the processing and sending sym-ops back to user.
But for CPU_CRYPTO it is not necessary, as all processing is synchronous and
user already has a pointer for related rte_ipsec_session.
We probably still can, but what is the benefit, who will use it?
Actually looking at the rte_ipsec_session_prepare() once again,
you probably right - it is a bug here, as we shouldn’t call rte_security_session_opaque_data_set()
for TYPE_CPU_CRYPTO.
So shouldn't it be like that:
ss->pkt_func = fp;
if (ss->type == RTE_SECURITY_ACTION_TYPE_NONE)
rte_cryptodev_sym_session_opaque_data_set(ss->crypto.ses,
(uintptr_t)ss);
- else
+ else if (ss->type != RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO)
rte_security_session_opaque_data_set(ss->security.ses, (uintptr_t)ss);
> Without the patch in rte_ipsec_session_prepare - for the
> RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO type, then ss->crypto.ses will not
> be set.
Hmm... not clear why?
AFAIK, ss->crypto.ses supposed to be set by user *before* calling rte_ipsec_session_prepare().
From lib/ipsec/rte_ipsec.h:
/**
* Checks that inside given rte_ipsec_session crypto/security fields
* are filled correctly and setups function pointers based on these values.
* Expects that all fields except IPsec processing function pointers
* (*pkt_func*) will be filled correctly by caller.
* @param ss
* Pointer to the *rte_ipsec_session* object
* @return
* - Zero if operation completed successfully.
* - -EINVAL if the parameters are invalid.
*/
int
rte_ipsec_session_prepare(struct rte_ipsec_session *ss);
>
> Regards,
>
> Garry.
>
>
> On Tue, Oct 31, 2023 at 1:09 AM Konstantin Ananyev
> <konstantin.v.ananyev@yandex.ru> wrote:
> >
> > >
> > >
> > > ipsec related processing in dpdk makes use of the crypto.ses opaque
> > > data pointer. This patch updates rte_ipsec_session_prepare to set
> > > ss->crypto.ses in the RTE_SECURITY_TYPE_CPU_CRYPTO case.
> >
> > Hmm.. not sure why we need to do that for CPU_CRYPTO?
> > As I remember CPU_CRYPTO is synchronous operation and before calling
> > rte_ipsec_pkt_cpu_prepare() should already know ipsec session these
> > packets belong to.
> > Can you probably explain the logic behind this patch a bit more?
> > Konstantin
> >
> > >
> > > Signed-off-by: Garry Marshall <gazmarsh@meaningfulname.net>
> > > ---
> > > lib/ipsec/ses.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/lib/ipsec/ses.c b/lib/ipsec/ses.c
> > > index d9ab1e6d2b..29eb5ff6ca 100644
> > > --- a/lib/ipsec/ses.c
> > > +++ b/lib/ipsec/ses.c
> > > @@ -44,7 +44,8 @@ rte_ipsec_session_prepare(struct rte_ipsec_session *ss)
> > >
> > > ss->pkt_func = fp;
> > >
> > > - if (ss->type == RTE_SECURITY_ACTION_TYPE_NONE)
> > > + if (ss->type == RTE_SECURITY_ACTION_TYPE_NONE ||
> > > + ss->type == RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO)
> > > rte_cryptodev_sym_session_opaque_data_set(ss->crypto.ses,
> > > (uintptr_t)ss);
> > > else
> > > --
> > > 2.39.2
next prev parent reply other threads:[~2023-10-31 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 20:11 Garry Marshall
2023-10-30 7:22 ` [EXT] " Akhil Goyal
2023-10-31 1:08 ` Konstantin Ananyev
2023-10-31 9:36 ` Garry Marshall
2023-10-31 17:53 ` Konstantin Ananyev [this message]
2023-11-02 7:20 ` Garry Marshall
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=de293a0aedd0408f9ea7dc8b733a4961@huawei.com \
--to=konstantin.ananyev@huawei.com \
--cc=dev@dpdk.org \
--cc=gazmarsh@meaningfulname.net \
--cc=konstantin.v.ananyev@yandex.ru \
--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).