public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Rolf Neugebauer <rolf.neugebauer@docker.com>
Cc: Borislav Petkov <bp@alien8.de>,
	Jia Zhang <zhang.jia@linux.alibaba.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Tony Luck <tony.luck@intel.com>, Ingo Molnar <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86/microcode/intel: Division by zero panic in 4.9.79 and 4.4.114
Date: Thu, 8 Feb 2018 17:39:14 +0100	[thread overview]
Message-ID: <20180208163914.GC9421@kroah.com> (raw)
In-Reply-To: <CA+pO-2eiim-6E8VLAV2K3s=pqEv7QcV1f8znLeQWqZh=zKWVVQ@mail.gmail.com>

On Wed, Feb 07, 2018 at 04:31:59PM +0000, Rolf Neugebauer wrote:
> On Wed, Feb 7, 2018 at 2:34 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Tue, Feb 06, 2018 at 03:24:44PM +0100, Borislav Petkov wrote:
> >> On Tue, Feb 06, 2018 at 02:09:35PM +0000, Rolf Neugebauer wrote:
> >> > The backport of 7e702d17ed1 ("x86/microcode/intel: Extend BDW
> >> > late-loading further with LLC size check") to 4.9.79 and 4.4.14 causes
> >> > a division by zero panic on some single vCPU machine types on Google
> >> > Cloud (e.g. g1-small and n1-standard-1):
> >>
> >> The microcode loader is not supposed to load in a guest.
> >>
> >> Greg, I guess you need something like this:
> >>
> >> a15a753539ec ("x86/microcode/AMD: Do not load when running on a hypervisor")
> >>
> >> I haven't tried whether it applies cleanly though...
> >
> > It applied cleanly to 4.9 (with some fuzz, but looks clean enough...)
> >
> > But for 4.4, not at all.  Rolf, any chance you could backport the patch
> > there for this issue?  If not, I can add it to my queue, but it might
> > take a few days...
> 
> The backport was straight forward. I've added it below. If my mailer
> (gmail) screws this up let me where I should send it with 'git
> send-email'

Yeah, it's messed up, can you resend it please?

thanks,

greg k-h

      parent reply	other threads:[~2018-02-08 16:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 14:09 x86/microcode/intel: Division by zero panic in 4.9.79 and 4.4.114 Rolf Neugebauer
2018-02-06 14:24 ` Borislav Petkov
2018-02-07 14:34   ` Greg KH
2018-02-07 16:31     ` Rolf Neugebauer
2018-02-07 18:12       ` Borislav Petkov
2018-02-08 13:55         ` Rolf Neugebauer
2018-02-08 14:53           ` Borislav Petkov
2018-02-08 16:25             ` Rolf Neugebauer
2018-02-08 16:39               ` Greg KH
2018-02-08 17:12                 ` [PATCH 1/2] x86/microcode/AMD: Do not load when running on a hypervisor Rolf Neugebauer
2018-02-08 17:12                   ` [PATCH 2/2] x86/microcode: Do the family check first Rolf Neugebauer
2018-02-08 17:25                     ` Greg KH
2018-02-08 18:26               ` x86/microcode/intel: Division by zero panic in 4.9.79 and 4.4.114 Borislav Petkov
2018-02-08 16:39       ` Greg KH [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=20180208163914.GC9421@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rolf.neugebauer@docker.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=zhang.jia@linux.alibaba.com \
    /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