From: Catalin Marinas <catalin.marinas@arm.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Vignesh R <vigneshr@ti.com>
Subject: Re: [PATCH] mm: kmemleak: Avoid using __va() on addresses that don't have a lowmem mapping
Date: Tue, 16 Aug 2016 18:31:44 +0100 [thread overview]
Message-ID: <20160816173143.GC7609@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <201608170130.HGiTRP7J%fengguang.wu@intel.com>
On Wed, Aug 17, 2016 at 01:15:53AM +0800, kbuild test robot wrote:
> [auto build test ERROR on mmotm/master]
> [also build test ERROR on v4.8-rc2 next-20160816]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Catalin-Marinas/mm-kmemleak-Avoid-using-__va-on-addresses-that-don-t-have-a-lowmem-mapping/20160816-232733
> base: git://git.cmpxchg.org/linux-mmotm.git master
> config: tile-tilegx_defconfig (attached as .config)
> compiler: tilegx-linux-gcc (GCC) 4.6.2
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=tile
>
> All error/warnings (new ones prefixed by >>):
>
> In file included from include/linux/kmemleak.h:24:0,
> from include/linux/slab.h:117,
> from arch/tile/include/asm/pgtable.h:27,
> from mm/init-mm.c:9:
> include/linux/mm.h: In function 'is_vmalloc_addr':
> include/linux/mm.h:486:17: error: 'VMALLOC_START' undeclared (first use in this function)
> include/linux/mm.h:486:17: note: each undeclared identifier is reported only once for each function it appears in
> include/linux/mm.h:486:41: error: 'VMALLOC_END' undeclared (first use in this function)
> include/linux/mm.h: In function 'maybe_mkwrite':
> include/linux/mm.h:624:3: error: implicit declaration of function 'pte_mkwrite'
> include/linux/mm.h:624:7: error: incompatible types when assigning to type 'pte_t' from type 'int'
> In file included from include/linux/kmemleak.h:24:0,
> from include/linux/slab.h:117,
> from arch/tile/include/asm/pgtable.h:27,
> from mm/init-mm.c:9:
It looks like some architectures don't really like including linux/mm.h
from linux/kmemleak.h. I'll change the patch to avoid this include and
explicitly declare high_memory in kmemleak.h
--
Catalin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-08-16 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 15:20 Catalin Marinas
2016-08-16 17:15 ` kbuild test robot
2016-08-16 17:31 ` Catalin Marinas [this message]
2016-08-16 17:27 ` kbuild test robot
2016-08-16 17:34 ` Catalin Marinas
2016-08-16 17:39 ` kbuild test robot
2016-08-17 15:51 ` [lkp] [mm] 122708b1b9: PANIC: early exception kernel test robot
2016-08-17 16:10 ` Catalin Marinas
2016-08-17 19:18 ` Andrew Morton
2016-08-17 20:36 ` Catalin Marinas
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=20160816173143.GC7609@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=vigneshr@ti.com \
/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