From: KY Srinivasan <kys@microsoft.com>
To: Florian Westphal <fw@strlen.de>, Feng Hong <hongfeng@marvell.com>
Cc: "ebiederm@xmission.com" <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: RE: Regression, bisected: hyperv shutdown panics guest
Date: Thu, 7 Feb 2013 12:43:27 +0000 [thread overview]
Message-ID: <fde89baf47fb4e44af86c784a4fafe91@SN2PR03MB061.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20130207105415.GD13962@breakpoint.cc>
> -----Original Message-----
> From: Florian Westphal [mailto:fw@strlen.de]
> Sent: Thursday, February 07, 2013 5:54 AM
> To: Feng Hong
> Cc: ebiederm@xmission.com; Kees Cook; linux-kernel@vger.kernel.org; KY
> Srinivasan; Haiyang Zhang
> 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@marvell.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
>
A patch has been submitted to fix this problem. It is in Greg's queue:
Subject: Re: [PATCH 6/6] Drivers: hv: Execute shutdown in a thread context
Regards,
K. Y
prev parent reply other threads:[~2013-02-07 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 10:54 Florian Westphal
2013-02-07 12:43 ` KY Srinivasan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fde89baf47fb4e44af86c784a4fafe91@SN2PR03MB061.namprd03.prod.outlook.com \
--to=kys@microsoft.com \
--cc=ebiederm@xmission.com \
--cc=fw@strlen.de \
--cc=haiyangz@microsoft.com \
--cc=hongfeng@marvell.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®