All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ruddy <pruddy@vyatta.att-mail.com>
To: netdev@vger.kernel.org
Cc: roopa@cumulusnetworks.com, jiri@resnulli.us, stephen@networkplumber.org
Subject: [PATCH net-next 0/2] netlink: multicast join notifications
Date: Thu, 30 Aug 2018 10:35:43 +0100	[thread overview]
Message-ID: <20180830093545.29465-1-pruddy@vyatta.att-mail.com> (raw)

This patch is an update to https://patchwork.ozlabs.org/patch/571127/. The
previous patch was based on sending multicast MAC addresses in the
netlink messages to allow the programming of hardware. It was agreed to
rework this to use RTM_NEW/DELLINK messages which were more appropriate
for layer 2 addresses.
In the interim period it has become apparent that the applications actually
needs to see the L3 multicast addresses which are joined for FORUS
processing so this patch has been reworked to send the L3 multicast
addresses using RTM_NEW/DELADDR.
These new multicast L3 netlink notifications should use the IFA_MULTICAST
address type but this has been dropped in favour of IFA_ADDRESS as during
testing it was noticed that some applications - notably getaddrinfo in
lib6c assume that there is an IFA_ADDRESS in a RTM_NEW/DELADDR and
blindly dereference it.
Finally the RTM_GETADDR for both address families has been modified to
include the multicast l3 addresses.

Patrick Ruddy (2):
  netlink: ipv4 IGMP join notifications
  netlink: ipv6 MLD join notifications

 include/linux/igmp.h |  2 +
 net/ipv4/devinet.c   | 39 +++++++++++++------
 net/ipv4/igmp.c      | 90 ++++++++++++++++++++++++++++++++++++++++++++
 net/ipv6/addrconf.c  | 44 ++++++++++++++++------
 net/ipv6/mcast.c     | 66 ++++++++++++++++++++++++++++++++
 5 files changed, 218 insertions(+), 23 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-08-31  0:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30  9:35 Patrick Ruddy [this message]
2018-08-30  9:35 ` [PATCH net-next 1/2] netlink: ipv4 IGMP join notifications Patrick Ruddy
2018-08-30 16:44   ` Patrick Ruddy
2018-08-31  4:23   ` kbuild test robot
2018-08-31  4:52   ` kbuild test robot
2018-08-31 11:20   ` [PATCH net-next v2 1/2] netlink: ipv4 igmp " Patrick Ruddy
2018-08-31 11:20     ` [PATCH net-next v2 2/2] netlink: ipv6 MLD " Patrick Ruddy
2018-08-31 16:29     ` [PATCH net-next v2 1/2] netlink: ipv4 igmp " Roopa Prabhu
2018-09-02 11:18       ` Patrick Ruddy
2018-09-03 23:12         ` Roopa Prabhu
2018-09-04  7:54           ` Patrick Ruddy
2018-09-04 16:36           ` Patrick Ruddy
2018-09-06  9:10   ` [PATCH net-next v3 " Patrick Ruddy
2018-09-06  9:10     ` [PATCH net-next v3 2/2] netlink: ipv6 MLD " Patrick Ruddy
2018-09-07  3:40     ` [PATCH net-next v3 1/2] netlink: ipv4 igmp " Roopa Prabhu
2018-09-13 17:03       ` Roopa Prabhu
2018-09-13 17:49         ` Patrick Ruddy
2018-09-18 13:12         ` Patrick Ruddy
2018-09-20  4:47           ` David Ahern
2018-09-25  9:34             ` Patrick Ruddy
2018-09-26 17:23               ` Roopa Prabhu
2018-10-01 15:38                 ` Roopa Prabhu
2018-08-30  9:35 ` [PATCH net-next 2/2] netlink: ipv6 MLD " Patrick Ruddy
2018-08-31  5:35   ` kbuild test robot

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=20180830093545.29465-1-pruddy@vyatta.att-mail.com \
    --to=pruddy@vyatta.att-mail.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=stephen@networkplumber.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.