From: Mike Maloney <maloneykernel@gmail.com>
To: netdev@vger.kernel.org, davem@davemloft.net
Cc: Mike Maloney <maloney@google.com>
Subject: [PATCH netnext 0/3] packet: Add option to create new fanout group with unique id.
Date: Thu, 20 Apr 2017 15:25:43 -0400 [thread overview]
Message-ID: <20170420192546.5567-1-maloneykernel@gmail.com> (raw)
From: Mike Maloney <maloney@google.com>
Fanout uses a per net global namespace. A process that intends to create a
new fanout group can accidentally join an existing group. It is
not possible to detect this.
Add a socket option to specify on the first call to
setsockopt(..., PACKET_FANOUT, ...) to ensure that a new group is created.
Also add tests.
Mike Maloney (3):
selftests/net: cleanup unused parameter in psock_fanout
packet: add PACKET_FANOUT_FLAG_UNIQUEID to assign new fanout group id.
selftests/net: add tests for PACKET_FANOUT_FLAG_UNIQUEID
include/uapi/linux/if_packet.h | 1 +
net/packet/af_packet.c | 44 ++++++++++++++
tools/testing/selftests/net/psock_fanout.c | 93 ++++++++++++++++++++++++++----
3 files changed, 128 insertions(+), 10 deletions(-)
--
2.12.2.816.g2cccc81164-goog
next reply other threads:[~2017-04-20 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 19:25 Mike Maloney [this message]
2017-04-20 19:25 ` [PATCH netnext 1/3] selftests/net: cleanup unused parameter in psock_fanout Mike Maloney
2017-04-20 19:25 ` [PATCH netnext 3/3] selftests/net: add tests for PACKET_FANOUT_FLAG_UNIQUEID Mike Maloney
2017-04-21 14:59 ` [PATCH netnext 0/3] packet: Add option to create new fanout group with unique id Willem de Bruijn
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=20170420192546.5567-1-maloneykernel@gmail.com \
--to=maloneykernel@gmail.com \
--cc=davem@davemloft.net \
--cc=maloney@google.com \
--cc=netdev@vger.kernel.org \
/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.