From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751523AbdAaQkM (ORCPT <rfc822;w@1wt.eu>);
        Tue, 31 Jan 2017 11:40:12 -0500
Received: from mail-wj0-f193.google.com ([209.85.210.193]:34915 "EHLO
        mail-wj0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751323AbdAaQkB (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 31 Jan 2017 11:40:01 -0500
Date: Tue, 31 Jan 2017 17:39:56 +0100
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Mike Galbraith <efault@gmx.de>,
        Andrey Ryabinin <aryabinin@virtuozzo.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        LKML <linux-kernel@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/microcode: Do not access the initrd after it has
 been freed
Message-ID: <20170131163956.GC16162@gmail.com>
References: <20170125172321.fpy6cswq3ibqvfgo@pd.tnic>
 <16165aad-5990-51f9-4dc7-c4b68597a4d5@virtuozzo.com>
 <20170125192336.kmgxmwcffdo2gxrf@pd.tnic>
 <20170126165833.evjemhbqzaepirxo@pd.tnic>
 <7d07442a-c64e-797b-c8c4-ef453df30cde@virtuozzo.com>
 <20170127090915.zh7ct7cnvx2ds7qk@pd.tnic>
 <20170130084632.GA25091@gmail.com>
 <20170130093527.syjz7yldgndml7qb@pd.tnic>
 <20170131074355.GA17636@gmail.com>
 <20170131100122.r6ubk5z3t2vm3hxl@pd.tnic>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170131100122.r6ubk5z3t2vm3hxl@pd.tnic>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Borislav Petkov <bp@alien8.de> wrote:

> On Tue, Jan 31, 2017 at 08:43:55AM +0100, Ingo Molnar wrote:
> > (Cc:-ed Mike as this could explain his early boot crash/hang?
> >         Mike: please try -tip f18a8a0143b1 that I just pushed out. )
> 
> One other thing to try, Mike, is boot with "dis_ucode_ldr". See whether
> that makes it go away.
> 
> > Nice - I've updated the branch with your resolution. Could you please 
> > double-check the double checked resolution?
> 
> That's like quadruple-checked :-)

Yeah, so when I wrote that I was pondering whether that counts as triple or 
quadruple checked. I couldn't make up my mind ;-)

Thanks,

	Ingo