From: patchwork-bot+netdevbpf@kernel•org
To: Hangbin Liu <liuhangbin@gmail•com>
Cc: netdev@vger•kernel.org, mst@redhat•com, jasowang@redhat•com,
davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
maximmi@mellanox•com,
WillemdeBruijnwillemdebruijn.kernel@gmail•com,
bnemeth@redhat•com, mpattric@redhat•com, edumazet@google•com
Subject: Re: [PATCHv2 net-next] net/af_packet: add VLAN support for AF_PACKET SOCK_RAW GSO
Date: Tue, 26 Apr 2022 09:30:10 +0000 [thread overview]
Message-ID: <165096541092.4224.10118526739950405614.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220425014502.985464-1-liuhangbin@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat•com>:
On Mon, 25 Apr 2022 09:45:02 +0800 you wrote:
> Currently, the kernel drops GSO VLAN tagged packet if it's created with
> socket(AF_PACKET, SOCK_RAW, 0) plus virtio_net_hdr.
>
> The reason is AF_PACKET doesn't adjust the skb network header if there is
> a VLAN tag. Then after virtio_net_hdr_set_proto() called, the skb->protocol
> will be set to ETH_P_IP/IPv6. And in later inet/ipv6_gso_segment() the skb
> is dropped as network header position is invalid.
>
> [...]
Here is the summary with links:
- [PATCHv2,net-next] net/af_packet: add VLAN support for AF_PACKET SOCK_RAW GSO
https://git.kernel.org/netdev/net-next/c/dfed913e8b55
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:[~2022-04-26 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 1:45 [PATCHv2 net-next] net/af_packet: add VLAN support for AF_PACKET SOCK_RAW GSO Hangbin Liu
2022-04-25 6:21 ` Hangbin Liu
2022-04-25 13:49 ` Willem de Bruijn
2022-04-25 13:52 ` Michael S. Tsirkin
2022-04-26 9:30 ` 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=165096541092.4224.10118526739950405614.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=WillemdeBruijnwillemdebruijn.kernel@gmail$(echo .)com \
--cc=bnemeth@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jasowang@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=liuhangbin@gmail$(echo .)com \
--cc=maximmi@mellanox$(echo .)com \
--cc=mpattric@redhat$(echo .)com \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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