On Sun, 2 Sep 2007, Stephen Hemminger wrote:
Vendor module calls kernel api incorrectly. dev_set_promiscuity requires
that the calling thread hold rtnl mutex (ie call rtnl_lock). It's their bug,
netdev doesn't want to hear about it.
OK, that's all I needed to know. Thank you both for your comme
On Sun, 2007-09-02 at 18:05 +0200, Christian Kujau wrote:
> but given the amount of changes currently
> going into net/ I thought this might be interesting:
>
> [15604.137408] RTNL: assertion failed at net/core/dev.c (2595)
> [15604.138807] [] __dev_set_promiscuity+0xc2/0xd0
into net/ I thought this might be interesting:
>
> [15604.137408] RTNL: assertion failed at net/core/dev.c (2595)
> [15604.137772] [] show_trace_log_lvl+0x1a/0x30
> [15604.138121] [] show_trace+0x12/0x20
> [15604.138449] [] dump_stack+0x15/0x20
> [15604.138807]
vmware), I just
wanted to let you netdev guys know, because the only occurences I found
on the net were from 1999, but given the amount of changes currently
going into net/ I thought this might be interesting:
[15604.137408] RTNL: assertion failed at net/core/dev.c (2595)
[15604.137772
