Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754957AbcJ0TZ4 (ORCPT ); Thu, 27 Oct 2016 15:25:56 -0400 Received: from mail.skyhub.de ([78.46.96.112]:45689 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751584AbcJ0TZy (ORCPT ); Thu, 27 Oct 2016 15:25:54 -0400 Date: Thu, 27 Oct 2016 21:19:51 +0200 From: Borislav Petkov To: Bob Peterson Cc: Linus Torvalds , Andy Lutomirski , Andreas Gruenbacher , Peter Zijlstra , Andy Lutomirski , LKML , Steven Whitehouse , Mel Gorman , linux-mm Subject: Re: CONFIG_VMAP_STACK, on-stack struct, and wake_up_bit Message-ID: <20161027191951.zgcrcmvmla7ayeon@pd.tnic> References: <996124132.13035408.1477505043741.JavaMail.zimbra@redhat.com> <1731570270.13088320.1477515684152.JavaMail.zimbra@redhat.com> <20161026231358.36jysz2wycdf4anf@pd.tnic> <624629879.13118306.1477528645189.JavaMail.zimbra@redhat.com> <20161027123623.j2jri5bandimboff@pd.tnic> <411894642.13576957.1477594290544.JavaMail.zimbra@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <411894642.13576957.1477594290544.JavaMail.zimbra@redhat.com> User-Agent: NeoMutt/20161014 (1.7.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 970 Lines: 28 On Thu, Oct 27, 2016 at 02:51:30PM -0400, Bob Peterson wrote: > I couldn't recreate that first boot failure, even using .config.old, > and even after removing (rm -fR) my linux.git and untarring it from the > original tarball, doing a make clean, etc. Hmm, so it could also depend on the randomized offset as it is getting generated anew each boot. So you could try to boot a couple of times to see if the randomized offset is generated just right for the bug condition to match. I mean, it would be great if you try a couple times but even if you're unsuccessful, that's fine too - the fix is obviously correct and I've confirmed that it boots fine in my VM here. > The output before and after your new patch are the same (except for the times): > > # dmesg | grep -i microcode > [ 5.291679] microcode: microcode updated early to new patch_level=0x010000d9 That looks good. Thanks! -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.