> -----Original Message----- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Monday, October 22, 2012 7:34 PM > To: KY Srinivasan > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; > o...@aepfle.de; > a...@canonical.com; jasow...@redhat.com > Subject: Re: 3.7 RC1 > > On Mon, Oct 22, 2012 at 04:37:45PM -0700, K. Y. Srinivasan wrote: > > > > 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? > > Can you check 3.7-rc2? If that also fails, care to do a 'git bisect' > from 3.6 to 3.7-rc1 to find the problem patch?
Looks like this problem is fixed in rc2. Regards, K. Y -- 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/
