Patch "x86/mm/32: Set the '__vmalloc_start_set' flag in initmem_init()" has been added to the 4.11-stable tree

This is a note to let you know that I've just added the patch titled

    x86/mm/32: Set the '__vmalloc_start_set' flag in initmem_init()

to the 4.11-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:

     x86-mm-32-set-the-__vmalloc_start_set-flag-in-initmem_init.patch

and it can be found in the queue-4.11 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

From: Laura Abbott <[email protected]>
Date: Mon, 8 May 2017 14:23:16 -0700
Subject: x86/mm/32: Set the '__vmalloc_start_set' flag in initmem_init()

From: Laura Abbott <[email protected]>

commit 861ce4a3244c21b0af64f880d5bfe5e6e2fb9e4a upstream.

'__vmalloc_start_set' currently only gets set in initmem_init() when !CONFIG_NEED_MULTIPLE_NODES. This breaks detection of vmalloc address with virt_addr_valid() with CONFIG_NEED_MULTIPLE_NODES=y, causing a kernel crash:

[mm/usercopy] 517e1fbeb6: kernel BUG at arch/x86/mm/physaddr.c:78!

Set '__vmalloc_start_set' appropriately for that case as well.

---
 arch/x86/mm/numa_32.c |    1 +
 1 file changed, 1 insertion(+)

@@ -100,5 +100,6 @@ void __init initmem_init(void)
 	printk(KERN_DEBUG "High memory starts at vaddr %08lx\n",
 			(ulong) pfn_to_kaddr(highstart_pfn));
 
+	__vmalloc_start_set = true;
 	setup_bootmem_allocator();
 }

Patches currently in stable-queue which might be from [email protected] are

queue-4.11/x86-mm-32-set-the-__vmalloc_start_set-flag-in-initmem_init.patch