From: Akhil Goyal <gakhil@marvell.com>
To: Weiguo Li <liwg06@foxmail.com>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Cc: "piotrx.bronowski@intel.com" <piotrx.bronowski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] [PATCH] crypto/ipsec_mb: fix null pointer dereference
Date: Tue, 8 Feb 2022 21:44:14 +0000 [thread overview]
Message-ID: <CO6PR18MB4484893D52ABEA0002001E08D82D9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <tencent_7E11AE18371EF353FD88339DCBEFB7113C07@qq.com>
> Adjust memory check and use in a proper order to avoid
> null pointer dereference.
>
> Fixes: 918fd2f1466b ("crypto/ipsec_mb: move aesni_mb PMD")
>
> Signed-off-by: Weiguo Li <liwg06@foxmail.com>
> ---
This patch is a duplicate of a patch already submitted.
http://patches.dpdk.org/project/dpdk/patch/20220116194043.1388372-1-piotrx.bronowski@intel.com/
prev parent reply other threads:[~2022-02-08 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 16:30 Weiguo Li
2022-02-08 21:44 ` 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=CO6PR18MB4484893D52ABEA0002001E08D82D9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=liwg06@foxmail.com \
--cc=piotrx.bronowski@intel.com \
--cc=roy.fan.zhang@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).