diff options
author | Romain Francoise <romain@orebokech.com> | 2011-01-17 07:59:18 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2011-01-18 16:13:49 -0800 |
commit | 2fdc1c8093255f9da877d7b9ce3f46c2098377dc (patch) | |
tree | aaf2ce878a25db10ce5509d5e9931d6e68184f06 /drivers/net/ns83820.c | |
parent | 6aefc522a8680f7b5a794f14dc78d6eab1cfdc37 (diff) | |
download | op-kernel-dev-2fdc1c8093255f9da877d7b9ce3f46c2098377dc.zip op-kernel-dev-2fdc1c8093255f9da877d7b9ce3f46c2098377dc.tar.gz |
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 'drivers/net/ns83820.c')
0 files changed, 0 insertions, 0 deletions