All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@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>
Subject: [PATCH net-next 0/2] net: enable udp v6 sockets receiving v4 packets with UDP GRO
Date: Mon, 11 Jan 2021 20:38:47 +0800	[thread overview]
Message-ID: <cover.1610368263.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.

Xin Long (2):
  udp: call udp_encap_enable for v6 sockets when enabling encap
  Revert "bareudp: Fixed bareudp receive handling"

 drivers/net/bareudp.c    | 6 ------
 include/net/udp_tunnel.h | 3 +--
 net/ipv6/udp.c           | 4 +++-
 3 files changed, 4 insertions(+), 9 deletions(-)

-- 
2.1.0


             reply	other threads:[~2021-01-11 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 12:38 Xin Long [this message]
2021-01-11 12:38 ` [PATCH net-next 1/2] udp: call udp_encap_enable for v6 sockets when enabling encap Xin Long
2021-01-11 12:38   ` [PATCH net-next 2/2] Revert "bareudp: Fixed bareudp receive handling" Xin Long
2021-01-11 18:01   ` [PATCH net-next 1/2] udp: call udp_encap_enable for v6 sockets when enabling encap kernel test robot
2021-01-11 18:01     ` kernel test robot
2021-01-12  7:53     ` Xin Long
2021-01-12  7:53       ` Xin Long

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.1610368263.git.lucien.xin@gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-sctp@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.