From: Julien Gomes <julien@arista.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
nikolay@cumulusnetworks.com, Julien Gomes <julien@arista.com>
Subject: [PATCH net-next 0/3] ipmr/ip6mr: add Netlink notifications on cache reports
Date: Tue, 13 Jun 2017 10:08:19 -0700 [thread overview]
Message-ID: <20170613170822.16310-1-julien@arista.com> (raw)
Currently, all ipmr/ip6mr cache reports are sent through the
mroute/mroute6 socket only.
This forces the use of a single socket for mroute programming, cache
reports and, regarding ipmr, IGMP messages without Router Alert option
reception.
The present patches are aiming to send Netlink notifications in addition
to the existing igmpmsg/mrt6msg to give user programs a way to handle
cache reports in parallel with multiple sockets other than the
mroute/mroute6 socket.
Julien Gomes (3):
rtnetlink: add NEWCACHEREPORT message type
ipmr: add netlink notifications on igmpmsg cache reports
ip6mr: add netlink notifications on mrt6msg cache reports
include/uapi/linux/mroute.h | 11 ++++++++
include/uapi/linux/mroute6.h | 11 ++++++++
include/uapi/linux/rtnetlink.h | 3 ++
net/ipv4/ipmr.c | 63 ++++++++++++++++++++++++++++++++++++++++--
net/ipv6/ip6mr.c | 63 ++++++++++++++++++++++++++++++++++++++++--
security/selinux/nlmsgtab.c | 3 +-
6 files changed, 149 insertions(+), 5 deletions(-)
--
2.13.1
next reply other threads:[~2017-06-13 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 17:08 Julien Gomes [this message]
2017-06-13 17:08 ` [PATCH net-next 1/3] rtnetlink: add NEWCACHEREPORT message type Julien Gomes
2017-06-13 17:08 ` [PATCH net-next 2/3] ipmr: add netlink notifications on igmpmsg cache reports Julien Gomes
2017-06-14 7:56 ` Nicolas Dichtel
2017-06-14 21:08 ` Julien Gomes
2017-06-13 17:08 ` [PATCH net-next 3/3] ip6mr: add netlink notifications on mrt6msg " Julien Gomes
2017-06-14 12:04 ` [PATCH net-next 0/3] ipmr/ip6mr: add Netlink notifications on " Nikolay Aleksandrov
2017-06-14 21:51 ` Julien Gomes
2017-06-15 11:33 ` Nikolay Aleksandrov
2017-06-15 11:44 ` Nikolay Aleksandrov
2017-06-15 13:00 ` Nikolay Aleksandrov
2017-06-16 19:26 ` Julien Gomes
2017-06-17 13:35 ` Nikolay Aleksandrov
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=20170613170822.16310-1-julien@arista.com \
--to=julien@arista.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.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