aboutsummaryrefslogtreecommitdiffstats
path: root/net/ipv6/addrconf.c
diff options
context:
space:
mode:
authorLubomir Rintel <lkundrak@v3.sk>2019-01-21 14:54:20 +0100
committerDavid S. Miller <davem@davemloft.net>2019-01-22 20:42:39 -0800
commit7c62b8dd5ca89dabd9f455d19e663bad60951bd5 (patch)
treed375c83a0344f003e2cbe707c8c9da3672a8de78 /net/ipv6/addrconf.c
parentnet: altera_tse: fix connect_local_phy error path (diff)
downloadlinux-dev-7c62b8dd5ca89dabd9f455d19e663bad60951bd5.tar.xz
linux-dev-7c62b8dd5ca89dabd9f455d19e663bad60951bd5.zip
net/ipv6: lower the level of "link is not ready" messages
This message gets logged far too often for how interesting is it. Most distributions nowadays configure NetworkManager to use randomly generated MAC addresses for Wi-Fi network scans. The interfaces end up being periodically brought down for the address change. When they're subsequently brought back up, the message is logged, eventually flooding the log. Perhaps the message is not all that helpful: it seems to be more interesting to hear when the addrconf actually start, not when it does not. Let's lower its level. Signed-off-by: Lubomir Rintel <lkundrak@v3.sk> Acked-By: Thomas Haller <thaller@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv6/addrconf.c')
-rw-r--r--net/ipv6/addrconf.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index 0c9e20ac01ab..84c358804355 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -3495,8 +3495,8 @@ static int addrconf_notify(struct notifier_block *this, unsigned long event,
if (!addrconf_link_ready(dev)) {
/* device is not ready yet. */
- pr_info("ADDRCONF(NETDEV_UP): %s: link is not ready\n",
- dev->name);
+ pr_debug("ADDRCONF(NETDEV_UP): %s: link is not ready\n",
+ dev->name);
break;
}