diff options
author | Eric W. Biederman <ebiederm@aristanetworks.com> | 2011-03-21 18:23:34 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2011-03-21 18:23:34 -0700 |
commit | 9d2a8fa96a44ba242de3a6f56acaef7a40a97b97 (patch) | |
tree | 1fd01e0ef3da06d1508481aeb7c3c4994122dff9 /drivers/net/veth.c | |
parent | d5cd92448fded12c91f7574e49747c5f7d975a8d (diff) | |
download | linux-3.10-9d2a8fa96a44ba242de3a6f56acaef7a40a97b97.tar.gz linux-3.10-9d2a8fa96a44ba242de3a6f56acaef7a40a97b97.tar.bz2 linux-3.10-9d2a8fa96a44ba242de3a6f56acaef7a40a97b97.zip |
net ipv6: Fix duplicate /proc/sys/net/ipv6/neigh directory entries.
When I was fixing issues with unregisgtering tables under /proc/sys/net/ipv6/neigh
by adding a mount point it appears I missed a critical ordering issue, in the
ipv6 initialization. I had not realized that ipv6_sysctl_register is called
at the very end of the ipv6 initialization and in particular after we call
neigh_sysctl_register from ndisc_init.
"neigh" needs to be initialized in ipv6_static_sysctl_register which is
the first ipv6 table to initialized, and definitely before ndisc_init.
This removes the weirdness of duplicate tables while still providing a
"neigh" mount point which prevents races in sysctl unregistering.
This was initially reported at https://bugzilla.kernel.org/show_bug.cgi?id=31232
Reported-by: sunkan@zappa.cx
Signed-off-by: Eric W. Biederman <ebiederm@aristanetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/veth.c')
0 files changed, 0 insertions, 0 deletions