From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: jdorfman@google.com, eric.dumazet@gmail.com, davem@davemloft.net,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next 0/3] ip: add RECVFRAGSIZE cmsg
Date: Wed, 2 Nov 2016 11:02:15 -0400 [thread overview]
Message-ID: <1478098938-124108-1-git-send-email-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
On IP datagrams and raw sockets, when packets arrive fragmented,
expose the largest received fragment size through a new cmsg.
Protocols implemented on top of these sockets may use this, for
instance, to inform peers to lower MSS on platforms that silently
allow send calls to exceed PMTU and cause fragmentation.
Willem de Bruijn (3):
ipv4: add IP_RECVFRAGSIZE cmsg
ipv6: add IPV6_RECVFRAGSIZE cmsg
ipv6: on reassembly, record frag_max_size
include/linux/ipv6.h | 5 +++--
include/net/inet_sock.h | 1 +
include/uapi/linux/in.h | 1 +
include/uapi/linux/in6.h | 1 +
net/ipv4/ip_sockglue.c | 26 ++++++++++++++++++++++++++
net/ipv6/datagram.c | 5 +++++
net/ipv6/ipv6_sockglue.c | 8 ++++++++
net/ipv6/reassembly.c | 7 ++++++-
8 files changed, 51 insertions(+), 3 deletions(-)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-11-02 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 15:02 Willem de Bruijn [this message]
2016-11-02 15:02 ` [PATCH net-next 1/3] ipv4: add IP_RECVFRAGSIZE cmsg Willem de Bruijn
2016-11-02 15:52 ` Eric Dumazet
2016-11-02 15:02 ` [PATCH net-next 2/3] ipv6: add IPV6_RECVFRAGSIZE cmsg Willem de Bruijn
2016-11-02 15:53 ` Eric Dumazet
2016-11-02 15:02 ` [PATCH net-next 3/3] ipv6: on reassembly, record frag_max_size Willem de Bruijn
2016-11-02 15:55 ` Eric Dumazet
2016-11-03 19:41 ` [PATCH net-next 0/3] ip: add RECVFRAGSIZE cmsg David Miller
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=1478098938-124108-1-git-send-email-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jdorfman@google.com \
--cc=netdev@vger.kernel.org \
--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).