netdev - Re: net-next: warnings from sysctl_net

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] [day] [month] [year] [list]

Date:	Sun, 27 Feb 2011 10:45:55 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	David Miller <davem@...emloft.net>
Cc:	adobriyan@...il.com, netdev@...r.kernel.org
Subject: Re: net-next: warnings from sysctl_net_exit

On Sat, 26 Feb 2011 22:23:33 -0800 (PST)
David Miller <davem@...emloft.net> wrote:

> From: Stephen Hemminger <shemminger@...tta.com>
> Date: Sat, 26 Feb 2011 16:56:01 -0800
> 
> > Seeing lots of these messages in dmesg. Something is broken
> > recently in net-next.
> 
> Did you by change pull plain net-2.6 into that tree?  Because one
> commit which is in net-2.6 but not in net-next-2.6 catches my eye:
> 
> commit c486da34390846b430896a407b47f0cea3a4189c
> Author: Lucian Adrian Grijincu <lucian.grijincu@...il.com>
> Date:   Thu Feb 24 19:48:03 2011 +0000
> 
>     sysctl: ipv6: use correct net in ipv6_sysctl_rtcache_flush
>     
>     Before this patch issuing these commands:
>     
>       fd = open("/proc/sys/net/ipv6/route/flush")
>       unshare(CLONE_NEWNET)
>       write(fd, "stuff")
>     
>     would flush the newly created net, not the original one.
>     
>     The equivalent ipv4 code is correct (stores the net inside ->extra1).
>     Acked-by: Daniel Lezcano <daniel.lezcano@...e.fr>
>     
>     Signed-off-by: David S. Miller <davem@...emloft.net>
> 

I am building against pure net-next tree. Just checked by recloning.

-- 
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html