From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, samanthakumar@google.com,
edumazet@google.com, willemb@google.com
Subject: [PATCH net-next v2 0/3] udp: support SO_PEEK_OFF
Date: Tue, 5 Apr 2016 12:41:13 -0400 [thread overview]
Message-ID: <1459874476-92838-1-git-send-email-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
Support peeking at a non-zero offset for UDP sockets. Match the
existing behavior on Unix datagram sockets.
1/3 makes the sk_peek_offset functions safe to use outside locks
2/3 removes udp headers before enqueue, to simplify offset arithmetic
3/3 introduces SO_PEEK_OFFSET support, with Unix socket peek semantics.
Changes
v1->v2
- squash patches 3 and 4
Willem de Bruijn (1):
sock: convert sk_peek_offset functions to WRITE_ONCE
samanthakumar (2):
udp: remove headers from UDP packets before queueing
udp: enable MSG_PEEK at non-zero offset
include/linux/skbuff.h | 7 ++++++-
include/net/sock.h | 27 ++++++++++++++++-----------
include/net/udp.h | 9 +++++++++
net/core/datagram.c | 9 ++++++---
net/core/sock.c | 28 ++++++++++++++++++++++------
net/ipv4/af_inet.c | 1 +
net/ipv4/udp.c | 38 ++++++++++++++++++++------------------
net/ipv6/af_inet6.c | 1 +
net/ipv6/udp.c | 30 ++++++++++++++++--------------
9 files changed, 97 insertions(+), 53 deletions(-)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-04-05 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 16:41 Willem de Bruijn [this message]
2016-04-05 16:41 ` [PATCH net-next v2 1/3] sock: convert sk_peek_offset functions to WRITE_ONCE Willem de Bruijn
2016-04-05 16:41 ` [PATCH net-next v2 2/3] udp: remove headers from UDP packets before queueing Willem de Bruijn
2016-04-05 16:41 ` [PATCH net-next v2 3/3] udp: enable MSG_PEEK at non-zero offset Willem de Bruijn
2016-04-05 20:29 ` [PATCH net-next v2 0/3] udp: support SO_PEEK_OFF 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=1459874476-92838-1-git-send-email-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=samanthakumar@google.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).