From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, sunkan@zappa.cx
Subject: Re: [Bugme-new] [Bug 31232] New: /proc/sys/net/ipv6 has two neigh folders
Date: Wed, 16 Mar 2011 20:55:59 -0700 [thread overview]
Message-ID: <m1oc5a2yeo.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20110316152300.360f9240.akpm@linux-foundation.org> (Andrew Morton's message of "Wed, 16 Mar 2011 15:23:00 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Wed, 16 Mar 2011 22:06:34 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=31232
>>
>> Summary: /proc/sys/net/ipv6 has two neigh folders
>> Product: Networking
>> Version: 2.5
>> Kernel Version: 2.6.38
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: low
>> Priority: P1
>> Component: IPV6
>> AssignedTo: yoshfuji@linux-ipv6.org
>> ReportedBy: sunkan@zappa.cx
>> Regression: No
>>
>>
>> I noticed when looking for other things that there are two neigh folders in
>> /proc/sys/net/ipv6
>>
>> Reverting this commit removes the extra neigh folder:
>> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=bf36076a67db6d7423d09d861a072337866f0dd9
>>
>> I don't know how to fix this.
>> I tried removing the ',' on the row '.child = empty,' (looking at the other
>> rows it did seem like a typo to me).
>>
>> This did not change anything that I could see though.
>>
>> Here is the commit I believe introduced the bug:
Interesting.
This is definitely a bug. I suspect it may be another symptom of the
bug I was trying to fix. Something somewhere is messed up with the
neigh directory.
That extra neigh entry should serve as a mount point for any later neigh
entries that are registered, so the change should be fine.
I will see if I can make the time to look into this, as this new symptom
looks as nasty as the use after free problems I was seeing earlier.
Eric
>> --- a/net/ipv6/sysctl_net_ipv6.c
>> +++ b/net/ipv6/sysctl_net_ipv6.c
>> @@ -15,6 +15,8 @@
>> #include <net/addrconf.h>
>> #include <net/inet_frag.h>
>>
>> +static struct ctl_table empty[1];
>> +
>> static ctl_table ipv6_table_template[] = {
>> {
>> .procname = "route",
>> @@ -35,6 +37,12 @@ static ctl_table ipv6_table_template[] = {
>> .mode = 0644,
>> .proc_handler = proc_dointvec
>> },
>> + {
>> + .procname = "neigh",
>> + .maxlen = 0,
>> + .mode = 0555,
>> + .child = empty,
>> + },
>> { }
>> };
>>
>> @@ -152,7 +160,6 @@ static struct ctl_table_header *ip6_base;
>>
>> int ipv6_static_sysctl_register(void)
>> {
>> - static struct ctl_table empty[1];
>> ip6_base = register_sysctl_paths(net_ipv6_ctl_path, empty);
>> if (ip6_base == NULL)
>> return -ENOMEM;
>>
prev parent reply other threads:[~2011-03-17 3:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31232-10286@https.bugzilla.kernel.org/>
2011-03-16 22:23 ` [Bugme-new] [Bug 31232] New: /proc/sys/net/ipv6 has two neigh folders Andrew Morton
2011-03-17 3:55 ` Eric W. Biederman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1oc5a2yeo.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sunkan@zappa.cx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.