From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Parri <parri.andrea@gmail.com>
Cc: linux-kernel@vger.kernel.org, kys@microsoft.com,
haiyangz@microsoft.com, sthemmin@microsoft.com,
wei.liu@kernel.org, mikelley@microsoft.com,
skarade@microsoft.com, juvazq@microsoft.com,
linux-hyperv@vger.kernel.org, davem@davemloft.net,
kuba@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v2] hv_netvsc: Add (more) validation for untrusted Hyper-V values
Date: Tue, 19 Jan 2021 04:00:09 +0000 [thread overview]
Message-ID: <161102880915.24762.9624432085976985112.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210114202628.119541-1-parri.andrea@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Thu, 14 Jan 2021 21:26:28 +0100 you wrote:
> For additional robustness in the face of Hyper-V errors or malicious
> behavior, validate all values that originate from packets that Hyper-V
> has sent to the guest. Ensure that invalid values cannot cause indexing
> off the end of an array, or subvert an existing validation via integer
> overflow. Ensure that outgoing packets do not have any leftover guest
> memory that has not been zeroed out.
>
> [...]
Here is the summary with links:
- [v2] hv_netvsc: Add (more) validation for untrusted Hyper-V values
https://git.kernel.org/netdev/net-next/c/505e3f00c3f3
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-01-19 4:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 20:26 [PATCH v2] hv_netvsc: Add (more) validation for untrusted Hyper-V values Andrea Parri (Microsoft)
2021-01-16 4:30 ` Jakub Kicinski
2021-01-16 13:02 ` Andrea Parri
2021-01-17 15:10 ` Wei Liu
2021-01-17 17:41 ` Andrea Parri
2021-01-19 4:00 ` 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=161102880915.24762.9624432085976985112.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=john.fastabend@gmail.com \
--cc=juvazq@microsoft.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=parri.andrea@gmail.com \
--cc=skarade@microsoft.com \
--cc=songliubraving@fb.com \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
--cc=yhs@fb.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).