Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 21 Jun 2016 11:24:18 +0200
From: Arnd Bergmann <>
To: Andy Lutomirski <>
Cc:,,, Borislav Petkov <>, Nadav Amit <>, Kees Cook <>, Brian Gerst <>, "" <>, Linus Torvalds <>, Josh Poimboeuf <>, Jann Horn <>, Heiko Carstens <>
Subject: Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

On Monday, June 20, 2016 4:43:30 PM CEST Andy Lutomirski wrote:
> On my laptop, this adds about 1.5┬Ás of overhead to task creation,
> which seems to be mainly caused by vmalloc inefficiently allocating
> individual pages even when a higher-order page is available on the
> freelist.

Would it help to have a fixed virtual address for the stack instead
and map the current stack to that during a task switch, similar to
how we handle fixmap pages?

That would of course trade the allocation overhead for a task switch
overhead, which may be better or worse. It would also give "current"
a constant address, which may give a small performance advantage
but may also introduce a new attack vector unless we randomize it


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.