Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2061719pxb; Fri, 29 Jan 2021 12:02:55 -0800 (PST) X-Google-Smtp-Source: ABdhPJzPwbWa9Y6zEs+m4rUXbgad+UKFzQrJGYQPk2f+E+MFJaRAN0ISzEhjIMrcSO5TVdoePTjy X-Received: by 2002:a17:906:2898:: with SMTP id o24mr6199281ejd.215.1611950574929; Fri, 29 Jan 2021 12:02:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611950574; cv=none; d=google.com; s=arc-20160816; b=al7sLiEJgJi5hNB+bLU6o8DEPAwuZ5gmcZxDneKvi2g/6xR9QvxxPeesrFd91z0WZq 6j5eFMX+CrnJ3diQB3jmbZ3ueGXVXW/HPSSthvUfqg4oW4Fzjl1MCvc3/sxDfx3NBAqw /VGaC/+jjK9A0E5FAUAF/riZxU/3zb5h15V8uTYnvLE2FVEFfLpiUsBvvdsFbjf7nMp9 f8Qq0ewjwDyGZgNk4uT3aqHiMX0KufRJtOHKCbQhY86HfSjMtQ15FzF0sGBOR5NqAiR1 Z+OY+PBshO7Ya0z9uOsvlAaPUU/f7fcpwAVo20IQhFz7nqtQvfUphN0YbIKByqWR5y0F Nd6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :to:subject:ironport-sdr:ironport-sdr; bh=NsSg+T7ALmNlte4ljSgfkzyKIV3Tbe8S3yEsIW3F/0c=; b=Kw5CyJDfolJ+zABb1G0ZPjgMm4KMWLXoxj0qSVTvPYOapQL0ObbgHAp5S7N37TJ0qI YSycj/WNiktjO0rVDqtBx112KzTdyQe71iUdqmoW4hzTTJifs0w4bqw0U/8g+FYrt1zl QMDs0ol5BnkX4ZhteRfzRe7/VkHF9xPG1oSqkyXvvUR+zqVfxsuQvVUV1gR4F/KaZW5v S27KYDByjdix4+4Bov/CJW3cGY5InlQfZeIKbg5wLdB/42voYIDV1NSSYEiEfJvUYsa9 ijSwOlc4d+nBOz+EaKarxMsj6nsuwImdgArKZIWhmcICW2aIXagjHuXETwJroGLqng0i vcPA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p4si5543062eja.208.2021.01.29.12.02.30; Fri, 29 Jan 2021 12:02:54 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232949AbhA2T7c (ORCPT + 99 others); Fri, 29 Jan 2021 14:59:32 -0500 Received: from mga11.intel.com ([192.55.52.93]:23678 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233130AbhA2Txv (ORCPT ); Fri, 29 Jan 2021 14:53:51 -0500 IronPort-SDR: zjf70VXaAEIUV36ih8JId+3Rp4ydDgb8CEOqNeIzlRUeuGGDKEZM2xsRKzmQQcATOQqZ/3o+Xs uFlRFG62DaNg== X-IronPort-AV: E=McAfee;i="6000,8403,9879"; a="176968696" X-IronPort-AV: E=Sophos;i="5.79,386,1602572400"; d="scan'208";a="176968696" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2021 11:53:08 -0800 IronPort-SDR: +mj39OBP743gPD+7++bzmhvPPBqDOqmZztGCGnQxxTqwCoqylBM8mo9huhwBKWmuMHuPIE18m+ pKgnaNZAm7ew== X-IronPort-AV: E=Sophos;i="5.79,386,1602572400"; d="scan'208";a="410848169" Received: from yyu32-mobl1.amr.corp.intel.com (HELO [10.212.73.214]) ([10.212.73.214]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2021 11:53:02 -0800 Subject: Re: [PATCH v18 24/25] x86/cet/shstk: Add arch_prctl functions for shadow stack To: Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, Arnd Bergmann , Andy Lutomirski , Balbir Singh , Borislav Petkov , Cyrill Gorcunov , Dave Hansen , Eugene Syromiatnikov , Florian Weimer , "H.J. Lu" , Jann Horn , Jonathan Corbet , Kees Cook , Mike Kravetz , Nadav Amit , Oleg Nesterov , Pavel Machek , Peter Zijlstra , Randy Dunlap , "Ravi V. Shankar" , Vedvyas Shanbhogue , Dave Martin , Weijiang Yang , Pengfei Xu References: <20210127212524.10188-1-yu-cheng.yu@intel.com> <20210127212524.10188-25-yu-cheng.yu@intel.com> <761ae8ce-0560-24cc-e6f7-684475cb3708@intel.com> <179fe87e-8fd1-9a26-e4f6-a508b45a54d4@intel.com> From: "Yu, Yu-cheng" Message-ID: <8d8bccab-12f3-0ecb-f2b2-91c26f82958a@intel.com> Date: Fri, 29 Jan 2021 11:53:01 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: <179fe87e-8fd1-9a26-e4f6-a508b45a54d4@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/29/2021 11:15 AM, Dave Hansen wrote: > On 1/29/21 10:56 AM, Yu, Yu-cheng wrote: >> On 1/29/2021 9:07 AM, Dave Hansen wrote: >>> On 1/27/21 1:25 PM, Yu-cheng Yu wrote: [...] >>> What's the point of doing copy_status_to_user() if the processor doesn't >>> support CET?  In other words, shouldn't this be below the CPU feature >>> check? >> >> The thought was to tell the difference between the kernel itself does >> not support CET and the system does not have CET.  And, if the kernel >> supports it, show CET status of the thread. > > Why would that matter to userspace? > > If they want to know if the processor has CET support there are existing > ways to do it. I don't think this should be part of the ABI. > Ok, I will make it: if (!cpu_feature_enabled(X86_FEATURE_CET)) ...