On Mon, 5 Aug 2002, Rusty Russell wrote:
>
> In testing, I came up against the "spin_unlock() causes schedule()
> inside interrupt" problem.
It shouldn't cause a schedule, it should cause a big warning (with
complete trace) to be printed out. Or did you mean something else?
Maybe the warning should be changed to
Warning, kernel is mixing metaphors. "It's not rocket surgery".
to make it clear why it's a bad idea.
Linus
-
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 : Wed Aug 07 2002 - 22:00:28 EST