From: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
To: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Cc: Mahesh Bandewar <maheshb@google.com>,
Jiri Benc <jbenc@redhat.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: [PATCH 0/3] ipvlan: fix ipv6 autoconfiguration via RA
Date: Thu, 14 May 2015 16:56:16 +0300 [thread overview]
Message-ID: <20150514134657.14062.87579.stgit@buzz> (raw)
This patchset fixes ipvlan and its interaction with ipv6 RA. Now ipvlan l2
ports get dev_id and construct unique ipv6 addresses using one mac address.
---
Konstantin Khlebnikov (3):
ipv6: make inet6addr_chain blocking and always call with rtnl locked
ipvlan: grab rcu_read_lock on xmit path
ipvlan: set dev_id for l2 ports to generate unique IPv6 addresses
Documentation/networking/ipvlan.txt | 12 +++++++++++-
drivers/net/ipvlan/ipvlan.h | 1 +
drivers/net/ipvlan/ipvlan_main.c | 24 ++++++++++++++++++++++++
net/ipv6/addrconf.c | 7 ++++---
net/ipv6/addrconf_core.c | 8 ++++----
5 files changed, 44 insertions(+), 8 deletions(-)
--
Konstantin
next reply other threads:[~2015-05-14 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 13:56 Konstantin Khlebnikov [this message]
2015-05-14 13:56 ` [PATCH 1/3] ipv6: make inet6addr_chain blocking and always call with rtnl locked Konstantin Khlebnikov
2015-05-16 21:22 ` David Miller
2015-05-18 10:13 ` Konstantin Khlebnikov
2015-05-14 13:56 ` [PATCH 2/3] ipvlan: grab rcu_read_lock on xmit path Konstantin Khlebnikov
2015-05-19 23:33 ` Mahesh Bandewar
2015-05-21 9:51 ` Konstantin Khlebnikov
2015-05-21 11:47 ` Hannes Frederic Sowa
2015-05-14 13:56 ` [PATCH 3/3] ipvlan: set dev_id for l2 ports to generate unique IPv6 addresses Konstantin Khlebnikov
2015-05-19 23:59 ` Mahesh Bandewar
2015-05-21 11:38 ` Konstantin Khlebnikov
2015-05-21 12:09 ` Hannes Frederic Sowa
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=20150514134657.14062.87579.stgit@buzz \
--to=khlebnikov@yandex-team.ru \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jbenc@redhat.com \
--cc=maheshb@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.