Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 21 Sep 2018 11:46:39 -0700
From: Kees Cook <>
To: Rick Edgecombe <>
Cc: Thomas Gleixner <>, Ingo Molnar <>, 
	"H. Peter Anvin" <>, X86 ML <>, LKML <>, 
	Linux-MM <>, Kernel Hardening <>, 
	Daniel Borkmann <>, Jann Horn <>, 
	Alexei Starovoitov <>, 
	Kristen Carlson Accardi <>, Dave Hansen <>, 
	Arjan van de Ven <>, Matthew Wilcox <>
Subject: Re: [PATCH v6 1/4] vmalloc: Add __vmalloc_node_try_addr function

On Thu, Sep 13, 2018 at 2:31 PM, Rick Edgecombe
<> wrote:
> Create __vmalloc_node_try_addr function that tries to allocate at a specific
> address and supports caller specified behavior for whether any lazy purging
> happens if there is a collision.
> This new function draws from the __vmalloc_node_range implementation. Attempts
> to merge the two into a single allocator resulted in logic that was difficult
> to follow, so they are left separate.
> Signed-off-by: Rick Edgecombe <>

Reviewed-by: Kees Cook <>

I'd love to get some more mm folks to look this over too.


Kees Cook
Pixel Security

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.