diff options
| author | Romain Francoise <romain@orebokech.com> | 2011-01-17 07:59:18 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-05-09 15:55:38 -0700 |
| commit | 390a91e54402a1aefd22f1e943b02da83be3e5dc (patch) | |
| tree | c8bf949fd32959aad325fc5cbe13bdb176caafbe /scripts | |
| parent | 9c392599a8c89467a1cc43cf41d74d1910c30a8f (diff) | |
ipv6: Silence privacy extensions initialization
commit 2fdc1c8093255f9da877d7b9ce3f46c2098377dc upstream.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions