While testing 3.7 RC1 I discovered that invoking the function orderly_poweroff() from an interrupt context will trigger an ASSERT(). This was not the case till recently. The comment preceding the orderly_poweroff() function claims that this function can be invoked from any context and in the current Hyper-V util driver, we support host-driven orderly shut down of the guest by invoking this orderly_poweroff() function in the context of the message callback. This code has been working for a very long time and it is broken now. Is my assumption that orderly_poweroff() could be invoked from the interrupt context a wrong assumption?
Regards, K. Y _______________________________________________ devel mailing list [email protected] http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
