From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?5YiY5rC45b+XIDxseXpfY3NAcGt1LmVkdS5jbj4=?=@ci.codeaurora.org
Cc: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
sashal@kernel.org, linux-hyperv@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
fuyq@stu.pku.edu.cn
Subject: Re: [PATCH] hv_netvsc: Fix potential dereference of NULL pointer
Date: Sat, 21 May 2022 01:00:12 +0000 [thread overview]
Message-ID: <165309481208.5645.11194329096449346020.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1652962188-129281-1-git-send-email-lyz_cs@pku.edu.cn>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 19 May 2022 05:09:48 -0700 you wrote:
> The return value of netvsc_devinfo_get()
> needs to be checked to avoid use of NULL
> pointer in case of an allocation failure.
>
> Fixes: 0efeea5fb ("hv_netvsc: Add the support of hibernation")
>
> Signed-off-by: Yongzhi Liu <lyz_cs@pku.edu.cn>
>
> [...]
Here is the summary with links:
- hv_netvsc: Fix potential dereference of NULL pointer
https://git.kernel.org/netdev/net/c/eb4c07889647
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-05-21 1:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 12:09 [PATCH] hv_netvsc: Fix potential dereference of NULL pointer Yongzhi Liu
2022-05-19 13:45 ` Haiyang Zhang
2022-05-21 1:00 ` patchwork-bot+netdevbpf [this message]
2022-05-20 17:13 [PATCH v2] iio: vadc: " Jonathan Cameron
2022-05-21 3:31 ` [PATCH] hv_netvsc: " Yongzhi Liu
2022-05-21 3:34 ` 刘永志
2022-05-23 15:21 ` Andy Shevchenko
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=165309481208.5645.11194329096449346020.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?5YiY5rC45b+XIDxseXpfY3NAcGt1LmVkdS5jbj4=?=@ci.codeaurora.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=fuyq@stu.pku.edu.cn \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.