[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpUxHX71GRmnmcvXpOX4P4mzJXpoYmcYhcZi2CXxEK4XFQ@mail.gmail.com>
Date: Mon, 7 Mar 2016 16:26:01 -0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Michal Kubecek <mkubecek@...e.cz>
Cc: "David S. Miller" <davem@...emloft.net>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
Martin KaFai Lau <kafai@...com>
Subject: Re: [PATCH net-next 2/3] ipv6: per netns fib6 walkers
On Fri, Mar 4, 2016 at 2:59 AM, Michal Kubecek <mkubecek@...e.cz> wrote:
> static void ipv6_route_seq_setup_walk(struct ipv6_route_iter *iter)
> {
> +#ifdef CONFIG_NET_NS
> + struct net *net = iter->p.net;
> +#else
> + struct net *net = &init_net;
> +#endif
> +
You should pass the struct net pointer to ipv6_route_seq_setup_walk()
instead of reading it by yourself.
I don't find anyone actually using iter->p, it probably can be just removed.
Powered by blists - more mailing lists