From: Oliver Hartkopp <oliver@xxxxxxxxxxxx>
Date: Mon, 05 Jan 2009 14:28:30 +0100
> 2. I got this inconsistent lock state, i've not seen before:
I know what causes it. It's this change:
commit 22604c866889c4b2e12b73cbf1683bda1b72a313
Author: Michael Marineau <mike@xxxxxxxxxxxx>
Date: Sun Jan 4 17:18:51 2009 -0800
net: Fix for initial link state in 2.6.28
It causes us to now call the linkwatch even trigger code inside of
software interrupt context, but that is illegal because that code path
takes the dev_base_lock rwlock as a writer.
I'm going to revert, and Michael will need to find a way to fix the
initial link state issue without adding locking problems :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
