From: kbuild test robot <lkp@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Guo Ren <ren_guo@c-sky.com>, Juergen Gross <jgross@suse.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 293/305] mm/sparse.c:440:69: warning: format '%lx' expects argument of type 'long unsigned int', but argument 6 has type 'long long unsigned int'
Date: Fri, 1 Feb 2019 00:19:36 +0800 [thread overview]
Message-ID: <201902010029.XV7WpeKw%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: a4186de8d65ec2ca6c39070ef1d6795a0b4ffe04
commit: 143cfc886d8275787a78aca1b2aa6053a1f00d3c [293/305] treewide: add checks for the return value of memblock_alloc*()
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 8.2.0-11) 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 143cfc886d8275787a78aca1b2aa6053a1f00d3c
# save the attached .config to linux build tree
GCC_VERSION=8.2.0 make.cross ARCH=arm64
All warnings (new ones prefixed by >>):
mm/sparse.c: In function 'sparse_buffer_init':
>> mm/sparse.c:440:69: warning: format '%lx' expects argument of type 'long unsigned int', but argument 6 has type 'long long unsigned int' [-Wformat=]
panic("%s: Failed to allocate %lu bytes align=0x%lx nid=%d from=%lx\n",
~~^
%llx
vim +440 mm/sparse.c
431
432 static void __init sparse_buffer_init(unsigned long size, int nid)
433 {
434 WARN_ON(sparsemap_buf); /* forgot to call sparse_buffer_fini()? */
435 sparsemap_buf =
436 memblock_alloc_try_nid_raw(size, PAGE_SIZE,
437 __pa(MAX_DMA_ADDRESS),
438 MEMBLOCK_ALLOC_ACCESSIBLE, nid);
439 if (!sparsemap_buf)
> 440 panic("%s: Failed to allocate %lu bytes align=0x%lx nid=%d from=%lx\n",
441 __func__, size, PAGE_SIZE, nid, __pa(MAX_DMA_ADDRESS));
442
443 sparsemap_buf_end = sparsemap_buf + size;
444 }
445
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 41973 bytes --]
reply other threads:[~2019-01-31 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201902010029.XV7WpeKw%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=hannes@cmpxchg.org \
--cc=jgross@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=ren_guo@c-sky.com \
--cc=rppt@linux.ibm.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