From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: adobriyan@gmail.com, netdev@vger.kernel.org
Subject: Re: net-next: warnings from sysctl_net_exit
Date: Sun, 27 Feb 2011 10:45:55 -0800 [thread overview]
Message-ID: <20110227104555.328f5d75@nehalam> (raw)
In-Reply-To: <20110226.222333.59680338.davem@davemloft.net>
On Sat, 26 Feb 2011 22:23:33 -0800 (PST)
David Miller <davem@davemloft.net> wrote:
> From: Stephen Hemminger <shemminger@vyatta.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@gmail.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@free.fr>
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
I am building against pure net-next tree. Just checked by recloning.
--
next prev parent reply other threads:[~2011-02-27 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 0:56 net-next: warnings from sysctl_net_exit Stephen Hemminger
2011-02-27 6:23 ` David Miller
2011-02-27 18:45 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-27 22:37 Lucian Adrian Grijincu
2011-02-27 23:34 ` David Miller
2011-02-28 0:49 ` Lucian Adrian Grijincu
2011-02-28 0:08 ` Stephen Hemminger
2011-02-28 1:11 ` Lucian Adrian Grijincu
2011-02-28 22:02 ` Stephen Hemminger
2011-03-02 7:09 ` Stephen Hemminger
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=20110227104555.328f5d75@nehalam \
--to=shemminger@vyatta.com \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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.