linux-kernel - 3.7 RC1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1350949065-24655-1-git-send-email-kys@microsoft.com>
Date:	Mon, 22 Oct 2012 16:37:45 -0700
From:	"K. Y. Srinivasan" <kys@...rosoft.com>
To:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
	jasowang@...hat.com
Subject: 3.7 RC1 

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/