From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Weiguo Li <liwg06@foxmail.com>, <jgrajcia@cisco.com>
Cc: <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v2] net/memif: remove pointer deference before null check
Date: Wed, 9 Feb 2022 17:51:35 +0000 [thread overview]
Message-ID: <1f351896-1cfb-0e15-29a8-206c7f20de27@intel.com> (raw)
In-Reply-To: <1ab6f6c4-7284-4ee4-8828-7bd9e98baccd@intel.com>
On 2/9/2022 1:56 PM, Ferruh Yigit wrote:
> On 2/9/2022 7:39 AM, Weiguo Li wrote:
>> There are duplicates of assignment here, the one before null check
>> may cause a null pointer deference, so remove the previous one.
>>
>> Fixes: 09c7e63a71f9 ("net/memif: introduce memory interface PMD")
>>
>
> Cc: stable@dpdk.org
>
>> Signed-off-by: Weiguo Li <liwg06@foxmail.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-02-09 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 7:27 [PATCH] " Weiguo Li
2022-02-09 7:39 ` [PATCH v2] " Weiguo Li
2022-02-09 13:56 ` Ferruh Yigit
2022-02-09 17:51 ` Ferruh Yigit [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=1f351896-1cfb-0e15-29a8-206c7f20de27@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=liwg06@foxmail.com \
--cc=stable@dpdk.org \
/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).