From: Uladzislau Rezki <urezki@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 8475/9410] ERROR: "__vmalloc_node_range" [lib/test_vmalloc.ko] undefined!
Date: Tue, 19 Feb 2019 09:54:41 +0100 [thread overview]
Message-ID: <20190219085441.s6bg2gpy4esny5vw@pc636> (raw)
In-Reply-To: <201902190637.nP67rDcw%fengguang.wu@intel.com>
Hello, Andrew.
On Tue, Feb 19, 2019 at 06:04:38AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: cb916fc5eabf8832e05f73c246eb467259846ef0
> commit: bd7e49fa421950084fff786200b7fd6872d51643 [8475/9410] vmalloc: add test driver to analyse vmalloc allocator
> config: h8300-allyesconfig (attached as .config)
> compiler: h8300-linux-gcc (GCC) 8.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout bd7e49fa421950084fff786200b7fd6872d51643
> # save the attached .config to linux build tree
> GCC_VERSION=8.2.0 make.cross ARCH=h8300
>
> All errors (new ones prefixed by >>):
>
> ERROR: "__divdi3" [lib/test_vmalloc.ko] undefined!
> >> ERROR: "__vmalloc_node_range" [lib/test_vmalloc.ko] undefined!
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
Could you please apply below patch to fix the error?
From f6ac7bddfc5969b0982ddf52ab248a1abb0b90a8 Mon Sep 17 00:00:00 2001
From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Date: Tue, 19 Feb 2019 09:47:51 +0100
Subject: [PATCH] lib/Kconfig.debug: make CONFIG_TEST_VMALLOC depends on
CONFIG_MMU
The vmalloc test driver can not be used on no-MMU systems. Add that
dependency to prevent the driver to be compiled on such systems.
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
---
lib/Kconfig.debug | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 960ba0cb58c4..618c3ee466e6 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1913,6 +1913,7 @@ config TEST_LKM
config TEST_VMALLOC
tristate "Test module for stress/performance analysis of vmalloc allocator"
default n
+ depends on MMU
depends on m
help
This builds the "test_vmalloc" module that should be used for
--
2.11.0
Sorry for inconvenience.
--
Vlad Rezki
prev parent reply other threads:[~2019-02-19 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 22:04 kbuild test robot
2019-02-19 8:54 ` Uladzislau Rezki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190219085441.s6bg2gpy4esny5vw@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox