> Applied to 2.4.8-pre1. Didn't make any difference.
Yes, that hole is mostly theoretical. At least, on intel. Seems, gcc is still
not enough clever to reorder atomic operations.
> Also it doesn't fix the scenario that I described (reschedule while running). I'm still wondering why don't I hit that trylock/BUG
> in tasklet_action.
How old the problem is? Was it always present?
To be honest, this is too strong bug to believe to this at all. :-)
Alexey
-
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/