[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fde89baf47fb4e44af86c784a4fafe91@SN2PR03MB061.namprd03.prod.outlook.com>
Date: Thu, 7 Feb 2013 12:43:27 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Florian Westphal <fw@...len.de>, Feng Hong <hongfeng@...vell.com>
CC: "ebiederm@...ssion.com" <ebiederm@...ssion.com>,
Kees Cook <keescook@...omium.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Haiyang Zhang <haiyangz@...rosoft.com>
Subject: RE: Regression, bisected: hyperv shutdown panics guest
> -----Original Message-----
> From: Florian Westphal [mailto:fw@...len.de]
> Sent: Thursday, February 07, 2013 5:54 AM
> To: Feng Hong
> Cc: ebiederm@...ssion.com; Kees Cook; linux-kernel@...r.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@...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
>
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
--
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/
Powered by blists - more mailing lists