[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52DD9CCB.3050101@redhat.com>
Date: Mon, 20 Jan 2014 23:01:47 +0100
From: Daniel Borkmann <dborkman@...hat.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: davem@...emloft.net, netdev@...r.kernel.org,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
Cong Wang <xiyou.wangcong@...il.com>
Subject: Re: [PATCH net-next] net: vxlan: do not use vxlan_net before checking
event type
On 01/20/2014 10:51 PM, Eric W. Biederman wrote:
...
> I am not going to argue against this patch as an immediate bug fix but
> something smells here, that bears deeper investigation. It looks like
> the symptom is being patched rather than the actual problem.
>
> In particular net_generic(dev_net(dev), vxlan_net_id) is valid at the
> point that it is being called. As the pointers are allocated in
> copy_net_ns in net_alloc prior to setup_net being called.
>
> On the flip side it is the responsibility of code that uses both
> register_netdev_notifier and register_pernet_xxx to be ready to handle
> events from any namespace as soon as they happen. vxlan should be using
> register_pernet_subsys instead of register_pernet_device to ensure the
> vxlan_net structure is initialized before and cleaned up after all
> network devices in a given network namespace. The vlan devices with a
> similar problem already do this.
>
> So in summary. Something smells and I don't believe this patch fixes
> the underlying issue. Please take a deeper look into what vxlan is doing.
Thanks for the input Eric!
If no-one is faster than me, I'll try to look into it soon.
--
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
Powered by blists - more mailing lists