linux-kernel - Regression, bisected: hyperv shutdown panics guest

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: <20130207105415.GD13962@breakpoint.cc>
Date:	Thu, 7 Feb 2013 11:54:15 +0100
From:	Florian Westphal <fw@...len.de>
To:	Feng Hong <hongfeng@...vell.com>
Cc:	ebiederm@...ssion.com, Kees Cook <keescook@...omium.org>,
	linux-kernel@...r.kernel.org, kys@...rosoft.com,
	haiyangz@...rosoft.com
Subject: Regression, bisected: hyperv shutdown panics guest

With 3.7, hyperv guest shutdown no longer works.
Instead, guest kernel throws a bunch of "BUG: scheduling-while-atomic"
errors and then dies.

reverting

commit 6c0c0d4d1080840eabb3d055d2fd81911111c5fd
Author: hongfeng <hongfeng@...vell.com>
Date:   Thu Oct 4 17:12:25 2012 -0700
poweroff: fix bug in orderly_poweroff()

fixes this problem.

Greping for users of orderly_poweroff() shows that hyperv isn't
the only caller that invokes the function from irq context.

In fact, kdoc for orderly_poweroff says:

* This may be called from any context to trigger a system shutdown.
* If the orderly shutdown fails, it will force an immediate shutdown.

Any suggestions on how to properly fix this?

Thanks,
Florian
--
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/