[PATCH] x86/mm: Set __vmalloc_start_set in numa_32.c

Path	csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Laura Abbott <labbott@redhat.com>
Newsgroups	linux.kernel
Subject	[PATCH] x86/mm: Set __vmalloc_start_set in numa_32.c
Date	Mon, 08 May 2017 23:30:02 +0200
Message-ID	<tEYoa-Pg-19@gated-at.bofh.it> (permalink)
References	<tEWmm-80A-25@gated-at.bofh.it>
X-Google-Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to; bh=/M8tCZLqS2S9V2oOGzCGkDe6qzyElKkV+6bbGDV5gJI=; b=Ff9U1OeSZX7nBgrtfKJiqb7CKY5zTC+mhIiqy7w381PTjW8dNbEImn1SMDnywBjefR GyJ0SfavohmiwZ28lYzYLb+QqSxkvUoiYO8+VfG/dfVHJjpSwY62HTbrmBxmyAOtA8B0 AVOYq4HL6+jOk5vDiWl/S5lYzEuodmQ9iWkPfruJRB5m0JzXt1zF6ryE/bYFdPxeVNaD YcW2GIiXRwsfK9ijmfdx73a1w6bF9nfrpeby5Ll+N8Kmc1OVImRZOV1QNtPGqRXQ02Bw QA/34PDN4qaEAU8w4txrfguTIkfs2zM2C6N5oTbyd1Hk5In7piMKX92OpwCnm4+kAPZg WB5g==
X-Gm-Message-State	AODbwcB+LHZdjiWxadnVqp/nDe29JSUfHpKsyPcJESPbP12wKjKNZWyE fw9/+P5VZ/r7RlLR
X-Received	by 10.55.130.131 with SMTP id e125mr29297733qkd.109.1494278606232; Mon, 08 May 2017 14:23:26 -0700 (PDT)
X-Mailer	git-send-email 2.7.4
Sender	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	25
Organization	linux.* mail to news gateway
X-Original-Cc	Laura Abbott <labbott@redhat.com>, x86@kernel.org, linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>
X-Original-Date	Mon, 8 May 2017 14:23:16 -0700
X-Original-Message-ID	<1494278596-30373-1-git-send-email-labbott@redhat.com>
X-Original-References	<CAGXu5jJQdf0KXKuTaqyH7YP=NL-0WYNKDYOZJSVjkjrYd4tG9A@mail.gmail.com>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	csiph.com linux.kernel:1637735

Show key headers only | View raw

__vmalloc_start_set currently only gets set in initmem_init when
!CONFIG_NEED_MULTIPLE_NODES. This currently breaks detection of vmalloc
address with virt_addr_valid with CONFIG_NEED_MULTIPLE_NODES=y.
Set __vmalloc_start_set appropriately for that case as well.

Fixes: dc16ecf7fd1f ("x86-32: use specific __vmalloc_start_set flag in __virt_addr_valid")q
Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
 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();
 }
-- 
2.7.4

Thread

Re: [mm/usercopy] 517e1fbeb6: kernel BUG at arch/x86/mm/physaddr.c:78! Kees Cook <keescook@chromium.org> - 2017-05-08 00:10 +0200
  Re: [mm/usercopy] 517e1fbeb6: kernel BUG at  arch/x86/mm/physaddr.c:78! Laura Abbott <labbott@redhat.com> - 2017-05-08 20:50 +0200
    Re: [mm/usercopy] 517e1fbeb6: kernel BUG at arch/x86/mm/physaddr.c:78! Kees Cook <keescook@chromium.org> - 2017-05-08 21:20 +0200
      [PATCH] x86/mm: Set __vmalloc_start_set in numa_32.c Laura Abbott <labbott@redhat.com> - 2017-05-08 23:30 +0200
        Re: [PATCH] x86/mm: Set __vmalloc_start_set in numa_32.c Kees Cook <keescook@chromium.org> - 2017-05-09 00:30 +0200
        [tip:x86/urgent] x86/mm/32: Set the '__vmalloc_start_set' flag in  initmem_init() tip-bot for Laura Abbott <tipbot@zytor.com> - 2017-05-09 08:50 +0200

csiph-web