On Tue, Feb 02, 2021 at 11:45:49AM -0800, Jakub Kicinski wrote:
On Tue, 2 Feb 2021 09:18:43 +0100 Andrea Parri wrote:
quoted
Hi net maintainers,
On Sat, Jan 30, 2021 at 12:50:06AM +0000, patchwork-bot+netdevbpf@kernel.org wrote:
quoted
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 26 Jan 2021 17:29:07 +0100 you wrote:
quoted
Pointers to receive-buffer packets sent by Hyper-V are used within the
guest VM. Hyper-V can send packets with erroneous values or modify
packet fields after they are processed by the guest. To defend against
these scenarios, copy (sections of) the incoming packet after validating
their length and offset fields in netvsc_filter_receive(). In this way,
the packet can no longer be modified by the host.
[...]
Here is the summary with links:
- [v2,net-next] hv_netvsc: Copy packets sent by Hyper-V out of the receive buffer
https://git.kernel.org/netdev/net-next/c/0ba35fe91ce3
I'd have some fixes on top of this and I'm wondering about the process: would
you consider fixes/patches on top of this commit now?
Fixes for bugs present in Linus's tree?
You need to target the net tree, and give us instructions on how to
resolve the conflict which will arise from merging net into net-next.
quoted
would you rather prefer me to squash these fixes into a v3? other?
Networking trees are immutable, and v2 was already applied. We could
do a revert, apply fix, apply v3, but we prefer to just handle the
merge conflict.
Thanks for the clarification, Jakub.
And sorry for the confusion; let me just send out the 'fixes'/patches (I
have one targeting the net tree and two targeting the net-next tree, with
no conflict between them), so that they can be reviewed and we can agree
/discuss any further steps.
Thanks,
Andrea