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 4CB9EC4332F for ; Tue, 8 Nov 2022 23:32:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230052AbiKHXco (ORCPT ); Tue, 8 Nov 2022 18:32:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40552 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229774AbiKHXck (ORCPT ); Tue, 8 Nov 2022 18:32:40 -0500 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3A46AE02 for ; Tue, 8 Nov 2022 15:32:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1667950359; x=1699486359; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=kzTE424pFzXVf9IENFeVVx4TxNlGGTb4uFNWa9RUX7s=; b=YRaKMpSN41sxL88h/+NklJFYBHd72qHAisLhZ+ClUXjvTdQ9eos+jmVp qn4nXUWzu7xy4l5sjxH9AntFVhMfEz8dDLHYts5OtZbtuQ5CtUp33LurL gzVbQOCTfH9YECeR55mPkoj5aLq3MJ9cEtgHilcnzl+nT6BmdaPBBOQNC wBaN7pwTx6bUnSDBZ0SOTXWDg5VQ7CWNi8WGH1ta6ZSNe5LEeBVkIt46l LeTk++jZyyZqLUQ+dO3lyYkMh65qx9cax0wKXAl115OSCUc+GOEgH4WxN HlzacfS859f76FvXB2q9nY+n4y5v81NCi2cVctfd1yZ+pwj9bFqtJFxUg g==; X-IronPort-AV: E=McAfee;i="6500,9779,10525"; a="312630635" X-IronPort-AV: E=Sophos;i="5.96,149,1665471600"; d="scan'208";a="312630635" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Nov 2022 15:32:38 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10525"; a="669732728" X-IronPort-AV: E=Sophos;i="5.96,149,1665471600"; d="scan'208";a="669732728" Received: from vibhusha-mobl1.amr.corp.intel.com (HELO [10.252.133.56]) ([10.252.133.56]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Nov 2022 15:32:38 -0800 Message-ID: <01fbc03e-bef0-bf07-d035-dac695800996@intel.com> Date: Tue, 8 Nov 2022 15:32:38 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: [v2 01/13] x86/microcode/intel: Prevent printing updated microcode rev multiple times Content-Language: en-US To: Ashok Raj , Borislav Petkov Cc: Thomas Gleixner , LKML Mailing List , X86-kernel , Tony Luck , Arjan van de Ven , Andy Lutomirski , Jacon Jun Pan , Tom Lendacky , Kai Huang , Andrew Cooper References: <20221103175901.164783-1-ashok.raj@intel.com> <20221103175901.164783-2-ashok.raj@intel.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/8/22 15:06, Ashok Raj wrote: > Patch3 is a bug fix. I suspect some earlier upstream reports of ucode > failure after update (early loading) might be related. The symptom is > similar, but those are too old to followup. I got into a similare situation > when i tried to update an incompatible uCode from initrd and system hung. Hi Ashok, If this really is a bug fix, could you please break it out and send it separately along with appropriate tags like Fixes and a cc:stable@? We handle bug fixes differently from new features.