From: patchwork-bot+netdevbpf@kernel.org
To: Guillaume Nault <gnault@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
martin.varghese@nokia.com, willemb@google.com
Subject: Re: [PATCH net v2 0/2] bareudp: Pull inner IP header on xmit/recv.
Date: Fri, 13 Sep 2024 03:40:29 +0000 [thread overview]
Message-ID: <172619882977.1805230.18095072533580961094.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1726046181.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 Sep 2024 11:20:51 +0200 you wrote:
> Bareudp accesses the inner IP header in its xmit and recv paths.
> However it doesn't ensure that this header is part of skb->head.
>
> Both vxlan and geneve have received fixes for similar problems in the
> past. This series fixes bareudp using the same approach.
>
> Guillaume Nault (2):
> bareudp: Pull inner IP header in bareudp_udp_encap_recv().
> bareudp: Pull inner IP header on xmit.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] bareudp: Pull inner IP header in bareudp_udp_encap_recv().
https://git.kernel.org/netdev/net/c/45fa29c85117
- [net,v2,2/2] bareudp: Pull inner IP header on xmit.
https://git.kernel.org/netdev/net/c/c471236b2359
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:[~2024-09-13 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 9:20 [PATCH net v2 0/2] bareudp: Pull inner IP header on xmit/recv Guillaume Nault
2024-09-11 9:20 ` [PATCH net v2 1/2] bareudp: Pull inner IP header in bareudp_udp_encap_recv() Guillaume Nault
2024-09-11 15:42 ` Willem de Bruijn
2024-09-11 9:21 ` [PATCH net v2 2/2] bareudp: Pull inner IP header on xmit Guillaume Nault
2024-09-11 15:43 ` Willem de Bruijn
2024-09-13 3:40 ` 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=172619882977.1805230.18095072533580961094.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=martin.varghese@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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).