[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130610.141421.1570141372448161465.davem@davemloft.net>
Date: Mon, 10 Jun 2013 14:14:21 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: stephen@...workplumber.org
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net v2 03/03] [PATCH] vxlan: fix crash on module removal
From: David Miller <davem@...hat.com>
Date: Mon, 10 Jun 2013 14:01:14 -0700 (PDT)
> From: Stephen Hemminger <stephen@...workplumber.org>
> Date: Mon, 10 Jun 2013 13:13:15 -0700
>
>> If vxlan is removed with active vxlan's it would crash because
>> rtnl_link_unregister (which calls vxlan_dellink), was invoked
>> before unregister_pernet_device (which calls vxlan_stop).
>>
>> Signed-off-by: Stephen Hemminger <stephen@...workplumber.org>
>> ---
>> Should goto stable
>
> Applied and queued up for -stable.
Actually, this doesn't even compile.
+ destroy_workqueue(vxlan_wq);
vxlan_wq doesn't exist in the 'net' tree.
It doesn't exist in net-next either.
It gets added as part of your vxlan-next series which you posted at
the same time.
I'm tossing both vxlan patch sets, you'll need to resubmit them
properly.
I'm tossing both becuase I can tell the -next one won't apply properly
on top of this series up when you fix it up.
--
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