From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3D90FC04A6A for ; Thu, 10 Aug 2023 20:54:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229486AbjHJUy4 (ORCPT ); Thu, 10 Aug 2023 16:54:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57054 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229379AbjHJUyy (ORCPT ); Thu, 10 Aug 2023 16:54:54 -0400 Received: from desiato.infradead.org (desiato.infradead.org [IPv6:2001:8b0:10b:1:d65d:64ff:fe57:4e05]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A476F26B5 for ; Thu, 10 Aug 2023 13:54:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=desiato.20200630; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=tVNc8xtFHD/5MjY48Rsdw7GPmJfCwnCNm1CX1ELPct4=; b=N++tONipnXKWQRJ4+lJlg8Vzy4 mEgbZ0/3eDZ145YfoFHWOfFJZXUda7P+lu+GTuYqxXQhaQNBSoxNSm6k8A61ynmOrpP9XxU6VfP7G UFBfQvsscREDozcZj1ccsxQTBz2QmvX4YwtQfO/lmKJARapwZ8Yv1Brh4Pnw6JXqfuQ1+oYYl9UrQ yAxFsP7avCwkstbShp8Nw7dsC8QsTk4XvFaEk8D4ptl+fszoPQKgARBgTHdsDZfScSih18QkCpbI/ Zt2Dx+cLPBMn0Yw2CuHrlEgOLiYhndNX/WyLuyKheJIxOQwNpMu/WRvw8ledQnp1i+dZahBXy+R1I LaSPUXog==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=noisy.programming.kicks-ass.net) by desiato.infradead.org with esmtpsa (Exim 4.96 #2 (Red Hat Linux)) id 1qUCfs-006kTI-1J; Thu, 10 Aug 2023 20:54:28 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id DD47630020B; Thu, 10 Aug 2023 22:54:27 +0200 (CEST) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id BE9922103B6B4; Thu, 10 Aug 2023 22:54:27 +0200 (CEST) Date: Thu, 10 Aug 2023 22:54:27 +0200 From: Peter Zijlstra To: Thomas Gleixner Cc: LKML , x86@kernel.org, Borislav Petkov , Ashok Raj , Arjan van de Ven Subject: Re: [patch 29/30] x86/microcode: Prepare for minimal revision check Message-ID: <20230810205427.GG212435@hirez.programming.kicks-ass.net> References: <20230810153317.850017756@linutronix.de> <20230810160806.617422055@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230810160806.617422055@linutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 10, 2023 at 08:38:09PM +0200, Thomas Gleixner wrote: > From: Thomas Gleixner > > Applying microcode late can be fatal for the running kernel when the update > changes functionality which is in use already in a non-compatible way, > e.g. by removing a CPUID bit. This includes all compatibility constraints? Because IIRC we've also had trouble because a CPUID bit got set. Kernel didn't know about, didn't manage it, but userspace saw the bit and happily tried to use it. Ofc I can't remember the exact case :/ but anything that changes the xsave size/state would obviously cause trouble.