summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorRomain Francoise <romain@orebokech.com>2011-01-17 07:59:18 +0000
committerDavid S. Miller <davem@davemloft.net>2011-01-18 16:13:49 -0800
commit2fdc1c8093255f9da877d7b9ce3f46c2098377dc (patch)
treeaaf2ce878a25db10ce5509d5e9931d6e68184f06 /net
parent6aefc522a8680f7b5a794f14dc78d6eab1cfdc37 (diff)
downloadlinux-2fdc1c8093255f9da877d7b9ce3f46c2098377dc.tar.bz2
ipv6: Silence privacy extensions initialization
When a network namespace is created (via CLONE_NEWNET), the loopback interface is automatically added to the new namespace, triggering a printk in ipv6_add_dev() if CONFIG_IPV6_PRIVACY is set. This is problematic for applications which use CLONE_NEWNET as part of a sandbox, like Chromium's suid sandbox or recent versions of vsftpd. On a busy machine, it can lead to thousands of useless "lo: Disabled Privacy Extensions" messages appearing in dmesg. It's easy enough to check the status of privacy extensions via the use_tempaddr sysctl, so just removing the printk seems like the most sensible solution. Signed-off-by: Romain Francoise <romain@orebokech.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
-rw-r--r--net/ipv6/addrconf.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index 5b189c97c2fc..24a1cf110d80 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -420,9 +420,6 @@ static struct inet6_dev * ipv6_add_dev(struct net_device *dev)
dev->type == ARPHRD_TUNNEL6 ||
dev->type == ARPHRD_SIT ||
dev->type == ARPHRD_NONE) {
- printk(KERN_INFO
- "%s: Disabled Privacy Extensions\n",
- dev->name);
ndev->cnf.use_tempaddr = -1;
} else {
in6_dev_hold(ndev);