From: Akhil Goyal <gakhil@marvell.com>
To: Ciara Power <ciara.power@intel.com>, Kai Ji <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.coyle@intel.com" <david.coyle@intel.com>,
Kevin O'Sullivan <kevin.osullivan@intel.com>
Subject: RE: [EXT] [PATCH] crypto/scheduler: fix session retrieval for ops
Date: Thu, 3 Nov 2022 08:11:12 +0000 [thread overview]
Message-ID: <CO6PR18MB448484A0D2ACFDE6CDA13384D8389@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221101164802.4094474-1-ciara.power@intel.com>
> In cases where some ops failed to enqueue, the op session was never being
> reset. This resulted in a segmentation fault when processing ops the
> next time. To fix this, only set the op session after the failure
> condition is checked.
>
> Also, the incorrect ops index was being used for session retrieval when
> dequeueing for the secondary worker.
>
> Fixes: 6812b9bf470e ("crypto/scheduler: use unified session")
>
> Reported-by: Kevin O'Sullivan <kevin.osullivan@intel.com>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2022-11-03 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 16:48 Ciara Power
2022-11-03 8:11 ` 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=CO6PR18MB448484A0D2ACFDE6CDA13384D8389@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ciara.power@intel.com \
--cc=david.coyle@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=kevin.osullivan@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).