Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

From	Jann Horn <jann@thejh.net>
Newsgroups	linux.kernel
Subject	Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)
Date	2016-09-06 18:20 +0200
Message-ID	<sergm-4jl-37@gated-at.bofh.it> (permalink)
References	(2 earlier) <rN1CW-2Rr-9@gated-at.bofh.it> <rN5ZU-5W6-25@gated-at.bofh.it> <rNdXs-2Tn-35@gated-at.bofh.it> <rNfPz-4cB-13@gated-at.bofh.it> <rNfZg-4gz-21@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Thu, Jun 23, 2016 at 09:41:11AM -0700, Andy Lutomirski wrote:
> 3. Free stacks immediately and cache them (really easy).

Random note: task_current_syscall() (via /proc/$pid/syscall) will probably need additional
locking when the stack is freed before the task.

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86,  core) Jann Horn <jann@thejh.net> - 2016-09-06 18:20 +0200
  Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core) Andy Lutomirski <luto@amacapital.net> - 2016-09-06 18:50 +0200

csiph-web