> Either we must demand that CPU 2 uses irq-safe spinlocks in order to
> protect against sk->write_space(),
> or we must demand that CPU 1 should drop
> 'lock1' before being allowed to call dev_kfree_skb_any().
Being pretty evident after seen once, this rule was _not_ evident for me
until yesterday. Actually, this is very sad observation, because core
has no way to detect this is a generic way...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/