> Also, we should be careful with things like up() on a semaphore which > hasn't been down()ed. Because under some Kconfig combinations, such an > operation might trigger debugging traces and we could get into a big > mess. (An up() on non-down()ed semaphore is actually an OK operation, > so this was a bad example. But you see the problem).
iirc the debugging code normally checks oops_in_progress, so this shouldn't happen. Agree on the rest of your email -- keep oops simple ... (KOSS) -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
