Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2598355rwb; Fri, 2 Dec 2022 12:04:48 -0800 (PST) X-Google-Smtp-Source: AA0mqf41aBt2Fx4J8+00h8QHYDxTlnVuODvYnfoiMZJxtT3JDivCqFiiwlTHnSPORsHVhPBkFcW4 X-Received: by 2002:aa7:cb0d:0:b0:45a:2d7c:f3a0 with SMTP id s13-20020aa7cb0d000000b0045a2d7cf3a0mr56153578edt.98.1670011488300; Fri, 02 Dec 2022 12:04:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670011488; cv=none; d=google.com; s=arc-20160816; b=ceJTGo6NGNav/Wfu3ZVBLGBxi1H+/ewFDUHdHfY4pBKdW87PV1BH3TPu3GTniCbrWB 5y4zuQdpbEeGhbe+FLYXozxUVeVLS9TYkfEPb09PQJKJ/jfNeBhy4nFZhyo1Ud1eD3P9 B1ynTnV/YX3ff6SmqA7CzPjhi7+7SNn3uxZaOc7i6FphXoKAXiqIO4bnUEHO5Yx0YfBA 39v/8M9peb8ApIrmXSiP+eEflLo2FRhtJ5HmS6bcJH+FaLnhOntBiBApcDVQf/OHz3A7 wz6MOvqM5iIxzz8iJWH5WvmQ8KX69fa+Icb/cS9EMq4zCv/rwXbeZr9DNO5TxDBhrAlc 96IA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=hGD3C2OE9Qr7B30PrUOZTVQpnPl/hR6oT6hCymS6mLQ=; b=GzSZdWAv7rSULoYWiyrAE7hURpyfBt9yQnCROtMFbup8wWyHRXifUa9WcmJwwVj7AV q5jBRN/e4+00GDdy1NZTZqpw8cS4snHSb47FwIF1fbsdq8EhZNmsXxN4QsNg/gIzTNHJ iWDtdeUHQJs3+4CxoRk2DwAnKMAtwDswPXD8Pxr97Qj6BmJa13m11/S5sR9cW0k2jvOe p9TcPqEIobHi+/IXpTmaDEe0C7VbBVoW2QHODSt0oJFgdO7HGhfmdgfuFOwrCrZbHhGD ZozkLKm/sLOSmfAD9TH7g7W6YQornw5qsNgxpUO7EgkIfgvBZr9bGsj5MTM+c/8MbFUe KYEQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=cP1lR3J1; dkim=neutral (no key) header.i=@linutronix.de header.b=Fi5AU0bx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id dt5-20020a170907728500b007bf9de4fe93si7238225ejc.154.2022.12.02.12.04.28; Fri, 02 Dec 2022 12:04:48 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=cP1lR3J1; dkim=neutral (no key) header.i=@linutronix.de header.b=Fi5AU0bx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234493AbiLBTCH (ORCPT + 82 others); Fri, 2 Dec 2022 14:02:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53962 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234788AbiLBTB5 (ORCPT ); Fri, 2 Dec 2022 14:01:57 -0500 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5B24FE2545 for ; Fri, 2 Dec 2022 11:01:56 -0800 (PST) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1670007715; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hGD3C2OE9Qr7B30PrUOZTVQpnPl/hR6oT6hCymS6mLQ=; b=cP1lR3J1+7x602QMu+R7Zmq6JJQ/tCP7vavRb9MLflK0KE3oiouqHqwrYM5cDQ3bZG0XAw u4iWqFXeDpQSZ02r0Qz6y8HmKPPz5vQcmSZcTK5YcDE032gG1Klw3EP9v1v7HI65pGTwP+ 3wR2w2zREpD7Ok9VQ8cYcLEChgTZmR/H5It/SMc4f6Fc1W0LfEZ65Hn6jQaL8WIEMbMPpB 7pySlj018ZY4tRuTBXroGx/fdc2K1JiBUPAUQt9Mje9iC1mfE4Oz263H3Hg9FHGB8Ar8wN XkNTZzbfcW56ZHRIKcxQsJUldvz3RMntI6ReMvWd8ihuJfnxvQOSA4cSWelfVA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1670007715; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hGD3C2OE9Qr7B30PrUOZTVQpnPl/hR6oT6hCymS6mLQ=; b=Fi5AU0bx2GJoGywQ/bKSnMtAADSdLFyl+TCsQN27Sc3jeLFZ50FsDuWQ4HrZbEQdFHzKmV aM0+nih/s5akZwAg== To: Ashok Raj , Borislav Petkov Cc: X86-kernel , LKML Mailing List , Ashok Raj , Dave Hansen , Tony Luck , alison.schofield@intel.com, reinette.chatre@intel.com Subject: Re: [Patch V1 2/7] x86/microcode/intel: Remove retries on early microcode load In-Reply-To: <20221129210832.107850-3-ashok.raj@intel.com> References: <20221129210832.107850-1-ashok.raj@intel.com> <20221129210832.107850-3-ashok.raj@intel.com> Date: Fri, 02 Dec 2022 20:01:54 +0100 Message-ID: <87a645pr31.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 29 2022 at 13:08, Ashok Raj wrote: > Microcode loading can fail. This happens today when handling mixed > steppings. But it can also happen for other reasons such as corrupted > image, Security Version Number (SVN) preventing anti-rollback, > dependencies on BIOS loaded microcode image for some capabilities. > > When the microcode loading fails, the kernel will quietly hang at boot. > This has been observed by end users (Links below) who had to revert their > microcode packages in order to boot again. > > The hang is due to an infinite retry loop. The retries were in place to > support systems with mixed steppings. Now that mixed steppings are no > longer supported, there is only one microcode image at a time. Any retries > will simply reattempt to apply the same image over and over without making > progress. > > Some possible past bugs that could be due to this bug are below. > > There is no direct evidence that these end user issues were caused by this > retry loop. However, the early boot hangs along with reverting the > microcode update workaround provide strong circumstantial evidence to > support the theory that they are linked. > > Remove the retry loop and only attempt to apply microcode once. Very concise and informative changelog. See, you can do it :) > Link: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911959 > Link: https://forums.linuxmint.com/viewtopic.php?p=1827032#1827032 > Link: https://askubuntu.com/questions/1291486/boot-crash-after-latest-update-of-intel-microcode-nov-11-2020 > Fixes: 06b8534cb728 ("x86/microcode: Rework microcode loading") > Cc: stable@vger.kernel.org > Signed-off-by: Ashok Raj Nit: Can you order the tags according to the tip documentation next time please? Reviewed-by: Thomas Gleixner