linux-kernel - Re: [ 163/171 ] ipv6: fix bad free of addrconf_init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 Sep 2013 14:36:40 +0800
From:	zhuyj <zyjzyj2000@...il.com>
To:	Hong Zhiguo <honkiko@...il.com>
CC:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org, "David S. Miller" <davem@...emloft.net>
Subject: Re: [ 163/171 ] ipv6: fix bad free of addrconf_init_net

On 04/12/2013 04:27 AM, Steven Rostedt wrote:
On linux with stable kernel v3.4.39, when this patch (ipv6: fix bad free 
of addrconf_init_net) is applied. Then I run the following commands:

1. the default value of ipv6 forwarding is 0

2. we change it to 1 firstly via:
# vi /etc/sysctl.conf
Uncomment: net.ipv6.conf.all.forwarding=1
#sysctl –p
Then we can verify via
#sysctl –a | grep forwarding

3, then we create a new namespace via:
# ip netns add fib_100
# ip netns exec fib_100 sysctl -a | grep forwarding

We’ll see in this new name space, the value of ipv6 forwarding will be 
set to ‘1’ in v3.4.38, but in v3.4.39, the value is still be ‘0’

without this patch (ipv6: fix bad free of addrconf_init_net), the value 
of ipv6 forwarding will be set to ‘1’.

Would you like to tell me which one (v4.3.39 and v4.3.38) is correct?

Best Regards!
Zhu Yanjun

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/