From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751861AbdEIGqQ (ORCPT ); Tue, 9 May 2017 02:46:16 -0400 Received: from terminus.zytor.com ([65.50.211.136]:35421 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751738AbdEIGqO (ORCPT ); Tue, 9 May 2017 02:46:14 -0400 Date: Mon, 8 May 2017 23:40:45 -0700 From: tip-bot for Laura Abbott Message-ID: Cc: tglx@linutronix.de, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, mingo@kernel.org, fengguang.wu@intel.com, keescook@chromium.org, peterz@infradead.org, hpa@zytor.com, labbott@redhat.com Reply-To: torvalds@linux-foundation.org, tglx@linutronix.de, fengguang.wu@intel.com, linux-kernel@vger.kernel.org, mingo@kernel.org, peterz@infradead.org, keescook@chromium.org, labbott@redhat.com, hpa@zytor.com In-Reply-To: <1494278596-30373-1-git-send-email-labbott@redhat.com> References: <1494278596-30373-1-git-send-email-labbott@redhat.com> To: linux-tip-commits@vger.kernel.org Subject: [tip:x86/urgent] x86/mm/32: Set the '__vmalloc_start_set' flag in initmem_init() Git-Commit-ID: 861ce4a3244c21b0af64f880d5bfe5e6e2fb9e4a X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: 861ce4a3244c21b0af64f880d5bfe5e6e2fb9e4a Gitweb: http://git.kernel.org/tip/861ce4a3244c21b0af64f880d5bfe5e6e2fb9e4a Author: Laura Abbott AuthorDate: Mon, 8 May 2017 14:23:16 -0700 Committer: Ingo Molnar CommitDate: Tue, 9 May 2017 08:12:27 +0200 x86/mm/32: Set the '__vmalloc_start_set' flag in initmem_init() '__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. Reported-by: kbuild test robot Signed-off-by: Laura Abbott Reviewed-by: Kees Cook Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Thomas Gleixner Fixes: dc16ecf7fd1f ("x86-32: use specific __vmalloc_start_set flag in __virt_addr_valid") Link: http://lkml.kernel.org/r/1494278596-30373-1-git-send-email-labbott@redhat.com Signed-off-by: Ingo Molnar --- arch/x86/mm/numa_32.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/mm/numa_32.c b/arch/x86/mm/numa_32.c index 6b7ce62..aca6295 100644 --- a/arch/x86/mm/numa_32.c +++ b/arch/x86/mm/numa_32.c @@ -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(); }