From: Xin Long <lucien.xin@gmail•com>
To: network dev <netdev@vger•kernel.org>
Cc: davem@davemloft•net, Jakub Kicinski <kuba@kernel•org>,
pabeni@redhat•com, Willem de Bruijn <willemb@google•com>,
Martin Varghese <martin.varghese@nokia•com>,
Alexander Duyck <alexander.duyck@gmail•com>,
David Howells <dhowells@redhat•com>
Subject: [PATCHv5 net-next 0/2] net: enable udp v6 sockets receiving v4 packets with UDP
Date: Wed, 3 Feb 2021 16:54:21 +0800 [thread overview]
Message-ID: <cover.1612342376.git.lucien.xin@gmail.com> (raw)
Currently, udp v6 socket can not process v4 packets with UDP GRO, as
udp_encap_needed_key is not increased when udp_tunnel_encap_enable()
is called for v6 socket.
This patchset is to increase it and remove the unnecessary code in
bareudp in Patch 1/2, and improve rxrpc encap_enable by calling
udp_tunnel_encap_enable().
v1->v4:
- See patch 1/2.
v4->v5:
- See patch 2/2.
Xin Long (2):
udp: call udp_encap_enable for v6 sockets when enabling encap
rxrpc: call udp_tunnel_encap_enable in rxrpc_open_socket
drivers/net/bareudp.c | 6 ------
include/net/udp.h | 1 +
include/net/udp_tunnel.h | 3 +--
net/ipv4/udp.c | 6 ++++++
net/ipv6/udp.c | 4 +++-
net/rxrpc/local_object.c | 7 ++-----
6 files changed, 13 insertions(+), 14 deletions(-)
--
2.1.0
next reply other threads:[~2021-02-03 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 8:54 Xin Long [this message]
2021-02-03 8:54 ` [PATCHv5 net-next 1/2] udp: call udp_encap_enable for v6 sockets when enabling encap Xin Long
2022-03-29 13:24 ` Antonio Quartulli
2022-03-29 13:30 ` Greg Kroah-Hartman
2022-03-31 13:06 ` Antonio Quartulli
2022-04-02 11:28 ` Greg Kroah-Hartman
2021-02-03 8:54 ` [PATCHv5 net-next 2/2] rxrpc: call udp_tunnel_encap_enable in rxrpc_open_socket Xin Long
2021-02-03 9:50 ` David Howells
2021-02-05 3:00 ` [PATCHv5 net-next 0/2] net: enable udp v6 sockets receiving v4 packets with UDP patchwork-bot+netdevbpf
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=cover.1612342376.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail$(echo .)com \
--cc=alexander.duyck@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dhowells@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=martin.varghese@nokia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=willemb@google$(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