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.