[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 10 Oct 2011 18:41:31 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Ben Greear <greearb@...delatech.com>
Cc: netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next] macvlan: handle fragmented multicast frames
Le lundi 10 octobre 2011 à 09:27 -0700, Ben Greear a écrit :
> I applied this to Linus' top-of-tree this morning and it does appear
> to fix the problem for mac-vlans.
>
Thanks for testing
> I do see this error, but I doubt it has anything to do with your
> patch:
>
> device eth0 entered promiscuous mode
> device rddVR10 entered promiscuous mode
> ADDRCONF(NETDEV_CHANGE): rddVR1b: link becomes ready
>
> ================================================
> [ BUG: lock held when returning to user space! ]
> ------------------------------------------------
> ip/3452 is leaving the kernel with locks still held!
> 1 lock held by ip/3452:
> #0: (rcu_read_lock){.+.+..}, at: [<f8c5336f>] rcu_read_lock+0x0/0x26 [ipv6]
> ADDRCONF(NETDEV_CHANGE): rddVR4b: link becomes ready
> ADDRCONF(NETDEV_CHANGE): rddVR5b: link becomes ready
>
>
> I have no idea why it doesn't print out a more useful stack
> trace. It seems repeatable (2 of 2 reboots so far). I'm
> configuring a pretty complex virtual network, with veth devices,
> xorp instances running ipv4 and ipv6 routing protocols, etc.
>
Do you have LOCKDEP enabled ?
> This is a clean upstream kernel with no outside patches aside from your
> own.
Hmm, it seems we have an rcu_read_unlock() missing...
Any idea what was done by this "ip" command ?
--
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