[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bbfde1b3-5e1b-80e3-30e8-fd1e46a2ceb1@gmail.com>
Date: Tue, 12 Jun 2018 20:56:30 +1000
From: Balbir Singh <bsingharora@...il.com>
To: Yu-cheng Yu <yu-cheng.yu@...el.com>, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-mm@...ck.org,
linux-arch@...r.kernel.org, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H.J. Lu" <hjl.tools@...il.com>,
Vedvyas Shanbhogue <vedvyas.shanbhogue@...el.com>,
"Ravi V. Shankar" <ravi.v.shankar@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...capital.net>,
Jonathan Corbet <corbet@....net>,
Oleg Nesterov <oleg@...hat.com>, Arnd Bergmann <arnd@...db.de>,
Mike Kravetz <mike.kravetz@...cle.com>
Subject: Re: [PATCH 00/10] Control Flow Enforcement - Part (3)
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.
Powered by blists - more mailing lists