From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: netdev@vger.kernel.org
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: [PATCH net-next] ipv6: recreate ipv6 link-local addresses when increasing MTU over IPV6_MIN_MTU
Date: Mon, 26 Oct 2015 15:36:45 +0100 [thread overview]
Message-ID: <1445870205-27202-1-git-send-email-hannes@stressinduktion.org> (raw)
Take into consideration that the interface might be disabled for IPv6,
thus switch event type.
Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
---
net/ipv6/addrconf.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index d0c685c..c2dcebe 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -3149,6 +3149,7 @@ static int addrconf_notify(struct notifier_block *this, unsigned long event,
case NETDEV_UP:
case NETDEV_CHANGE:
+netdev_change:
if (dev->flags & IFF_SLAVE)
break;
@@ -3244,8 +3245,10 @@ static int addrconf_notify(struct notifier_block *this, unsigned long event,
if (!idev && dev->mtu >= IPV6_MIN_MTU) {
idev = ipv6_add_dev(dev);
- if (!IS_ERR(idev))
- break;
+ if (!IS_ERR(idev)) {
+ event = NETDEV_UP;
+ goto netdev_change;
+ }
}
/*
--
2.5.0
next reply other threads:[~2015-10-26 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 14:36 Hannes Frederic Sowa [this message]
2015-10-26 15:52 ` [PATCH net-next] ipv6: recreate ipv6 link-local addresses when increasing MTU over IPV6_MIN_MTU Alexander Duyck
2015-10-26 16:05 ` Hannes Frederic Sowa
2015-10-26 17:07 ` Alexander Duyck
2015-10-26 17:21 ` Hannes Frederic Sowa
2015-10-26 19:05 ` Hannes Frederic Sowa
2015-10-26 16:33 ` Hannes Frederic Sowa
2015-10-26 19:16 ` Jay Vosburgh
2015-10-26 20:45 ` Hannes Frederic Sowa
2015-10-26 20:52 ` Alexander Duyck
2015-10-26 18:06 ` [net-next PATCH v2] " Alexander Duyck
2015-10-30 9:11 ` 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=1445870205-27202-1-git-send-email-hannes@stressinduktion.org \
--to=hannes@stressinduktion.org \
--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 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).