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 X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E4C35C433B4 for ; Tue, 18 May 2021 19:45:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CD317610FA for ; Tue, 18 May 2021 19:45:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351942AbhERTqr (ORCPT ); Tue, 18 May 2021 15:46:47 -0400 Received: from mga07.intel.com ([134.134.136.100]:27039 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1351956AbhERTqm (ORCPT ); Tue, 18 May 2021 15:46:42 -0400 IronPort-SDR: zQ0X6kd8P7C2v7/dKEdhUyu6nZleqfLe8HoacyZY7sYuZ1fXWE5a2cmr8gd6dxhn85RNBWp2dZ dVA1Hj5RFtvQ== X-IronPort-AV: E=McAfee;i="6200,9189,9988"; a="264720044" X-IronPort-AV: E=Sophos;i="5.82,310,1613462400"; d="scan'208";a="264720044" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 May 2021 12:45:18 -0700 IronPort-SDR: tYQi2B82XedKDm6qGiBjeEUdZVyLSN3ijHw1VG6+3/gOUcVnRwKduMlDNvjLJFTLm5urO60hXJ V5q6mwSq98IA== X-IronPort-AV: E=Sophos;i="5.82,310,1613462400"; d="scan'208";a="439600915" Received: from yyu32-mobl1.amr.corp.intel.com (HELO [10.209.166.158]) ([10.209.166.158]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 May 2021 12:45:16 -0700 Subject: Re: [PATCH v26 24/30] x86/cet/shstk: Introduce shadow stack token setup/verify routines To: Borislav Petkov , Eugene Syromiatnikov Cc: 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 , Cyrill Gorcunov , Dave Hansen , 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 , Haitao Huang References: <20210427204315.24153-1-yu-cheng.yu@intel.com> <20210427204315.24153-25-yu-cheng.yu@intel.com> <20210518001316.GR15897@asgard.redhat.com> From: "Yu, Yu-cheng" Message-ID: <10f74571-f8c4-9b08-0157-1570b30a1a6d@intel.com> Date: Tue, 18 May 2021 12:45:13 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/18/2021 10:58 AM, Borislav Petkov wrote: > On Tue, May 18, 2021 at 02:14:14AM +0200, Eugene Syromiatnikov wrote: >> Speaking of which, I wonder what would happen if a 64-bit process makes >> a 32-bit system call (using int 0x80, for example), and gets a signal. > > I guess that's the next patch. And I see amluto has some concerns... > > /me goes read. > In the next revision, there will be no "signal context extension" struct. However, the flow for 64, ia32 and x32 will be similar. I will send that out after some testing. Thanks, Yu-cheng