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 79488EB64DC for ; Wed, 19 Jul 2023 00:21:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229574AbjGSAV6 (ORCPT ); Tue, 18 Jul 2023 20:21:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42038 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229490AbjGSAV5 (ORCPT ); Tue, 18 Jul 2023 20:21:57 -0400 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F2F2E136; Tue, 18 Jul 2023 17:21:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1689726116; x=1721262116; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=pT6Ies0wLFEXJTKDZySE8hEP555Mfms46DvEBx71y1Q=; b=EfClzMjDcRHjh+CGIP4nECRW2oY1e5OMGAq3u01Qqf/VzKKYmWdZv5rm vOMQXF8cNLPfYK5+Oa6objnV9uzhqu1qeSoY7KcaTVrDjTlX7JK8SYoPf B1/ajuaKIvNfpWbkyuLn5aSVMBtE+vNzB/o0CC5yHWi/2r+x/6HB+/tfs sSYR45qAuLPh1xizE1bJALOuaVC3PrS6p9+8kS5y3XmRPYW9JxE+GqAhe cEvQ3gTLI0W4Xegt9IDrVkFAM5Qfzy8hgaiR+5uLBkOvDOr5ErkS4Qz91 jlgj9/PoC+o6alG2LCwqccjhJRv1R8HAnjMB8IpHnZkZu0ckgKoHXmKVI w==; X-IronPort-AV: E=McAfee;i="6600,9927,10775"; a="351210768" X-IronPort-AV: E=Sophos;i="6.01,215,1684825200"; d="scan'208";a="351210768" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jul 2023 17:21:56 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.01,202,1684825200"; d="scan'208";a="867275772" Received: from unknown (HELO [10.209.37.195]) ([10.209.37.195]) by fmsmga001-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jul 2023 17:21:55 -0700 Message-ID: Date: Tue, 18 Jul 2023 17:21:54 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: [PATCH] x86/sgx: fix a NULL pointer Content-Language: en-US To: "Huang, Kai" , "linux-sgx@vger.kernel.org" , "bp@alien8.de" , "dave.hansen@linux.intel.com" , "jarkko@kernel.org" , "x86@kernel.org" , "mingo@redhat.com" , "tglx@linutronix.de" , "hpa@zytor.com" , "haitao.huang@linux.intel.com" , "linux-kernel@vger.kernel.org" Cc: "kristen@linux.intel.com" , "Chatre, Reinette" , "stable@vger.kernel.org" , "Christopherson,, Sean" References: <20230717202938.94989-1-haitao.huang@linux.intel.com> <520111c9ccdd7356f9eaf20013e3e3c75b06398e.camel@intel.com> From: Dave Hansen In-Reply-To: <520111c9ccdd7356f9eaf20013e3e3c75b06398e.camel@intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-sgx@vger.kernel.org On 7/18/23 17:14, Huang, Kai wrote: > Also perhaps the patch title is too vague. Adding more information doesn't hurt > I think, e.g., mentioning it is a fix for NULL pointer dereference in the EAUG > flow. Yeah, let's say something like: x86/sgx: Resolve SECS reclaim vs. page fault race please