From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yu-cheng Yu Subject: Re: [PATCH 00/10] Control Flow Enforcement - Part (3) Date: Tue, 12 Jun 2018 08:03:40 -0700 Message-ID: <1528815820.8271.16.camel@2b52.sc.intel.com> 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: Sender: linux-kernel-owner@vger.kernel.org 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 List-Id: linux-arch.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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 Message-ID: <1528815820.8271.16.camel@2b52.sc.intel.com> Subject: Re: [PATCH 00/10] Control Flow Enforcement - Part (3) From: Yu-cheng Yu 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" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: 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 Message-ID: <20180612150340.D-nTfDhNcRJVIdtxtyd4PcXrUWXW2WJk6sa_yOuxTQw@z> 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.