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 46B70C05027 for ; Wed, 1 Feb 2023 18:28:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230189AbjBAS2G (ORCPT ); Wed, 1 Feb 2023 13:28:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34466 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230204AbjBAS2C (ORCPT ); Wed, 1 Feb 2023 13:28:02 -0500 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 04114AD25 for ; Wed, 1 Feb 2023 10:28:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1675276081; x=1706812081; h=message-id:date:mime-version:subject:to:references:from: in-reply-to:content-transfer-encoding; bh=KJfvR0PNRjVIZ5qVTjcc05Xxt8yxLl4gMU5LDLRTEu0=; b=ZS/BmpPImOtMdT7aj84rMFE3dBbAtFKv6JuwyLmzFHLEbiFb4zzgyPec WLr1R5ig/Tke6B1Oh8cZiHe21ykT1nh4CQTOKYCasz84xGbThSz1AWJ0B QmjEF7YbQrqkjUMDMsVz6REFAxPbJw5oQEMQxv0JoS8v39GlNQRng79Wp nKorZKkm6NhmjfwgHT4sLpsJgwOLqPJI1qrBfCZLThRE4HOe+PEMFUcDk Nry/u4iRTNuWL0doBEOxa2t4mPEFxOR++7q3r2TRb1wmpJt9ERMEn8nIS hmkmyJJiGxTaA2BiUbQ3z8kGbm0wvEx7b5wJfJfr21z/0LD6VPKhoIZ4V w==; X-IronPort-AV: E=McAfee;i="6500,9779,10608"; a="414437036" X-IronPort-AV: E=Sophos;i="5.97,265,1669104000"; d="scan'208";a="414437036" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2023 10:20:35 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10608"; a="667009268" X-IronPort-AV: E=Sophos;i="5.97,265,1669104000"; d="scan'208";a="667009268" Received: from sgkhacha-mobl1.amr.corp.intel.com (HELO [10.212.227.86]) ([10.212.227.86]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2023 10:20:34 -0800 Message-ID: Date: Wed, 1 Feb 2023 10:20:33 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH 3/7] x86/cpu: Disable kernel LASS when patching kernel alternatives Content-Language: en-US To: Sohil Mehta , "Chen, Yian" , linux-kernel@vger.kernel.org, x86@kernel.org, Andy Lutomirski , Dave Hansen , Ravi Shankar , Tony Luck , Paul Lai References: <20230110055204.3227669-1-yian.chen@intel.com> <20230110055204.3227669-4-yian.chen@intel.com> <693d8332-3b86-3dcf-fc87-5c3a08a752db@intel.com> <9e0a8b20-cb76-b06d-67fb-f8942df5a2f7@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 1/31/23 18:25, Sohil Mehta wrote: >> /* >> * Set cr4 to a known state: >> * - physical address extension enabled >> * - 5-level paging, if it was enabled before >> */ >> movl $X86_CR4_PAE, %eax >> testq $X86_CR4_LA57, %r13 >> jz 1f >> orl $X86_CR4_LA57, %eax >> 1: >> movq %rax, %cr4 >> >> jmp 1f >> 1: > Dave, does this address your concern or were you looking for something > else? Is there some path other than kexec that should also be audited > for this scenario? Yep, that addresses it. I don't know of any other path that would matter. Couldn't hurt to poke around and look for other CR4 manipulation that might need to be LASS-aware, though.