From: Shan Wei <shanwei@cn.fujitsu.com>
To: Lucian Adrian Grijincu <lucian.grijincu@gmail.com>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Daniel Lezcano <dlezcano@fr.ibm.com>,
Benjamin Thery <benjamin.thery@bull.net>
Subject: Re: [PATCH] sysctl: ipv6: use correct net in ipv6_sysctl_rtcache_flush
Date: Wed, 02 Mar 2011 11:25:18 +0800 [thread overview]
Message-ID: <4D6DB89E.6010709@cn.fujitsu.com> (raw)
In-Reply-To: <1298612883-18762-1-git-send-email-lucian.grijincu@gmail.com>
Lucian Adrian Grijincu wrote, at 02/25/2011 01:48 PM:
> 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.
After appling your patch, when excuting above commands,
router cache still not be flushed in init net namespace.
But IPv4 is ok.
Host1: Host2
ping6 Host2
(shell1)
open(/proc/sys/net/ipv6/route/flush)
unshare(CLONE_NEWNET)
while(1) {write(fd, "stuff")}
(shell2)
ip -6 route show cache <==1*
1*: IPv6 will show one route cache entry.
But IPv4 shows nothing.
As changlog said, after this patch, shell1 only fulsh the original
net namespace, not the newly created one. But from shell2, we
can see that IPv6 route cache is not flushed.
Have i missed something?
--
Best Regards
-----
Shan Wei
>
> The equivalent ipv4 code is correct (stores the net inside ->extra1).
> ---
> net/ipv6/route.c | 17 ++++++++++-------
> 1 files changed, 10 insertions(+), 7 deletions(-)
>
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index f786aed..522563e 100644
> --- a/net/ipv6/route.c
> +++ b/net/ipv6/route.c
> @@ -2604,14 +2604,16 @@ static
> int ipv6_sysctl_rtcache_flush(ctl_table *ctl, int write,
> void __user *buffer, size_t *lenp, loff_t *ppos)
> {
> - struct net *net = current->nsproxy->net_ns;
> - int delay = net->ipv6.sysctl.flush_delay;
> - if (write) {
> - proc_dointvec(ctl, write, buffer, lenp, ppos);
> - fib6_run_gc(delay <= 0 ? ~0UL : (unsigned long)delay, net);
> - return 0;
> - } else
> + struct net *net;
> + int delay;
> + if (!write)
> return -EINVAL;
> +
> + net = (struct net *)ctl->extra1;
> + delay = net->ipv6.sysctl.flush_delay;
> + proc_dointvec(ctl, write, buffer, lenp, ppos);
> + fib6_run_gc(delay <= 0 ? ~0UL : (unsigned long)delay, net);
> + return 0;
> }
>
> ctl_table ipv6_route_table_template[] = {
> @@ -2698,6 +2700,7 @@ struct ctl_table * __net_init ipv6_route_sysctl_init(struct net *net)
>
> if (table) {
> table[0].data = &net->ipv6.sysctl.flush_delay;
> + table[0].extra1 = net;
> table[1].data = &net->ipv6.ip6_dst_ops.gc_thresh;
> table[2].data = &net->ipv6.sysctl.ip6_rt_max_size;
> table[3].data = &net->ipv6.sysctl.ip6_rt_gc_min_interval;
next prev parent reply other threads:[~2011-03-02 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 5:48 [PATCH] sysctl: ipv6: use correct net in ipv6_sysctl_rtcache_flush Lucian Adrian Grijincu
2011-02-25 15:30 ` Daniel Lezcano
2011-02-25 19:02 ` David Miller
2011-03-02 3:25 ` Shan Wei [this message]
2011-03-02 16:38 ` Daniel Lezcano
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=4D6DB89E.6010709@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=benjamin.thery@bull.net \
--cc=davem@davemloft.net \
--cc=dlezcano@fr.ibm.com \
--cc=lucian.grijincu@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).