From mboxrd@z Thu Jan 1 00:00:00 1970 From: Balbir Singh Subject: Re: [PATCH 00/10] Control Flow Enforcement - Part (3) Date: Tue, 12 Jun 2018 20:56:30 +1000 Message-ID: References: <20180607143807.3611-1-yu-cheng.yu@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180607143807.3611-1-yu-cheng.yu@intel.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Yu-cheng Yu , 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 List-Id: linux-arch.vger.kernel.org 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f68.google.com ([209.85.160.68]:47051 "EHLO mail-pl0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932556AbeFLK4x (ORCPT ); Tue, 12 Jun 2018 06:56:53 -0400 Subject: Re: [PATCH 00/10] Control Flow Enforcement - Part (3) References: <20180607143807.3611-1-yu-cheng.yu@intel.com> From: Balbir Singh Message-ID: Date: Tue, 12 Jun 2018 20:56:30 +1000 MIME-Version: 1.0 In-Reply-To: <20180607143807.3611-1-yu-cheng.yu@intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: Yu-cheng Yu , 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 Message-ID: <20180612105630.E-LhDNGGYxIPcDrtUNt53xVYB-zkb7MW5NEGperZ1IA@z> 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.