From: Borislav Petkov <bp@alien8.de>
To: Rolf Neugebauer <rolf.neugebauer@docker.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
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 15:53:49 +0100 [thread overview]
Message-ID: <20180208145348.GC7964@pd.tnic> (raw)
In-Reply-To: <CA+pO-2e=nZJeAR2j8Pukb=E4aHgvDXc9Tw4poatrUcD15Wi1Jg@mail.gmail.com>
On Thu, Feb 08, 2018 at 01:55:48PM +0000, Rolf Neugebauer wrote:
> On the 4.4 kernel, 1f161f67a272c ("x86/microcode: Do the family check
> first") does not apply cleanly. Looks like it relies on 309aac77768c0
> ("x86/microcode: Decrease CPUID use") and 7a93a40be23e5
> ("x86/microcode: Remove local vendor variable") as well. These don't
> apply cleanly either.
It figures. The backporting game is hm, well, a fun one. :-)
> Should I just manually backport the functionality of 1f161f67a272c?
Yeah, try that first.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-02-08 14:53 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 [this message]
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
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=20180208145348.GC7964@pd.tnic \
--to=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--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