From: patchwork-bot+netdevbpf@kernel.org
To: Colin Ian King <colin.king@canonical.com>
Cc: yisen.zhuang@huawei.com, salil.mehta@huawei.com,
davem@davemloft.net, kuba@kernel.org, tanhuazhong@huawei.com,
zhangjiaran@huawei.com, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] net: hns3: Fix potential null pointer defererence of null ae_dev
Date: Mon, 12 Apr 2021 20:20:08 +0000 [thread overview]
Message-ID: <161825880895.1346.11497783869109240984.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210409163726.670672-1-colin.king@canonical.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 9 Apr 2021 17:37:26 +0100 you wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> The reset_prepare and reset_done calls have a null pointer check
> on ae_dev however ae_dev is being dereferenced via the call to
> ns3_is_phys_func with the ae->pdev argument. Fix this by performing
> a null pointer check on ae_dev and hence short-circuiting the
> dereference to ae_dev on the call to ns3_is_phys_func.
>
> [...]
Here is the summary with links:
- [next] net: hns3: Fix potential null pointer defererence of null ae_dev
https://git.kernel.org/netdev/net-next/c/d0494135f94c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-04-12 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 16:37 [PATCH][next] net: hns3: Fix potential null pointer defererence of null ae_dev Colin King
2021-04-12 20:20 ` patchwork-bot+netdevbpf [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=161825880895.1346.11497783869109240984.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=tanhuazhong@huawei.com \
--cc=yisen.zhuang@huawei.com \
--cc=zhangjiaran@huawei.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).