Mulix wrote:
>dev_kfree_skb_any() should be called when you could be either
>executing in interrupt context or not.
>
dev_kfree_skb_any() can misdetect the context: You must not use the
function if you hold an irq spinlock and you might be running from BH or
process context.
cpu 1: cpu 2:
acquire one of the networking bh lock
acquire the driver spin_lock_irq()
hardware interrupt
try to acquire the driver irq spinlock
--> spin.
dev_kfree_skb_any(): !in_irq(), calls kfree_skb
kfree_skb tries to acquire the network lock that
cpu 1 owns
--> spin.
And deadlock.
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Dec 31 2002 - 22:00:17 EST