Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp5459027imm; Tue, 12 Jun 2018 08:08:50 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKEnFgnNl+49zl7cLbMBKxXa+nitmsIId4WwlMu5n/sDIUs2MtOVgKCmbPkeCqobpY2BqhB X-Received: by 2002:a65:578c:: with SMTP id b12-v6mr645021pgr.315.1528816130166; Tue, 12 Jun 2018 08:08:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528816130; cv=none; d=google.com; s=arc-20160816; b=L11TzwYam7xKI8wFH81xBxYnyaB09PT9R1Isa4zGXHZWrRq6o+omCLlYohg8769wRR MAbkHwS4FoEcO+LHV7l/0LI4iOs/NWuQkuWPgqMWxD4Gt5h5aiBYFpEiSV5lshDEs6ri h4Q2CVeAoIZAn2A2nDuqSLw6pMASSQ/Iyks2LmVA73T0ROG+0vG9aB1EIpYOU1h1euW9 Pi+d+HRST664o6gIYecFJ0mAoUnDGX/QC9FWpZZAqIXg/GjT1B9xIa1Yvj5R3QRETde/ cgtmWKaTsOn7maAint8jv4tyGw1fCWTCPVH11ns/+XejsN8F/bDaL9OkTYfgdzgegE66 LtGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=w00xqJBEV7DEzRU0akOo7STk44VUi9Z33hq64noZkME=; b=aJkq940AFBRtZTc1m5f0amk19cL9etzLqAQ7zTUs/2uP571sZXk/OGfKw7uawfQZSg l68dMLRbvRIiG9bSS5x9rcRIuyJH5OQckbSkyjCeo3gZhF/tXXNnx2Ra/f1/u2NYBnXm 1Nqj2d2RwxuWcq1RyMTEAAoj6wwxch01XyvSHXfk9LHFS+VeGBcDw+v9OtiO8x7cSRIt 8wehsJoWH9yEA1lNXlvQyMUipchP1WMnxDI6RFPq3RnYaFhriB2aotdW3TRzLv1bS1r5 R0QZOk931tcTgBkBcLxOYQkynygR97z7XjEdYXMgF7MP6/uXIXYLhUzRpo3d8xl1GUla 0wjw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id x13-v6si344886pln.62.2018.06.12.08.08.35; Tue, 12 Jun 2018 08:08:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S934392AbeFLPGw (ORCPT + 99 others); Tue, 12 Jun 2018 11:06:52 -0400 Received: from mga04.intel.com ([192.55.52.120]:23629 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933363AbeFLPGt (ORCPT ); Tue, 12 Jun 2018 11:06:49 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2018 08:06:49 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,215,1526367600"; d="scan'208";a="46547133" Received: from 2b52.sc.intel.com (HELO [143.183.136.147]) ([143.183.136.147]) by fmsmga007.fm.intel.com with ESMTP; 12 Jun 2018 08:06:48 -0700 Message-ID: <1528815820.8271.16.camel@2b52.sc.intel.com> Subject: Re: [PATCH 00/10] Control Flow Enforcement - Part (3) From: Yu-cheng Yu To: Balbir Singh Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , "H.J. Lu" , Vedvyas Shanbhogue , "Ravi V. Shankar" , Dave Hansen , Andy Lutomirski , Jonathan Corbet , Oleg Nesterov , Arnd Bergmann , Mike Kravetz Date: Tue, 12 Jun 2018 08:03:40 -0700 In-Reply-To: References: <20180607143807.3611-1-yu-cheng.yu@intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2018-06-12 at 20:56 +1000, Balbir Singh wrote: > > On 08/06/18 00:37, Yu-cheng Yu wrote: > > This series introduces CET - Shadow stack > > > > At the high level, shadow stack is: > > > > Allocated from a task's address space with vm_flags VM_SHSTK; > > Its PTEs must be read-only and dirty; > > Fixed sized, but the default size can be changed by sys admin. > > > > For a forked child, the shadow stack is duplicated when the next > > shadow stack access takes place. > > > > For a pthread child, a new shadow stack is allocated. > > > > The signal handler uses the same shadow stack as the main program. > > > > Even with sigaltstack()? > > > Balbir Singh. Yes.