[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AEC0653.8050109@gmail.com>
Date: Sat, 31 Oct 2009 10:41:39 +0100
From: Eric Dumazet <eric.dumazet@...il.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: "David S. Miller" <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: [PATCH net-next-2.6] veth: Fix unregister_netdevice_queue for
veth
Eric W. Biederman a écrit :
> I tested the recent unregister many changes and got a weird,
> nasty and seemingly unrelasted kernel oops. Changing
> unregister_netdevice_queue to use list_move_tail fixes
> the problem for me.
>
> ip link add type veth
> rmmod veth
>
> ls /sys/class/net/
> showed one of the veth devices still present.
>
> A subsequent ip link oopsed the box.
>
> Signed-off-by: "Eric W. Biederman" <ebiederm@...ssion.com>
>
Yes, problem is __rtnl_kill_links() doesnt anymore restart
its loop and does :
for_each_netdev(net, dev) {
if (dev->rtnl_link_ops == ops)
ops->dellink(dev, &list_kill);
}
unregister_netdevice_many(&list_kill);
As veth wants in its dellink() method to unregister two netdevices,
we really want your fix or corrupt list_kill
Acked-by: Eric Dumazet <eric.dumazet@...il.com>
Thanks Eric
--
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