From: zijun_hu <zijun_hu@zoho.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org,
ard.biesheuvel@linaro.org, david@gibson.dropbear.id.au,
dev@g0hl1n.net, kuleshovmail@gmail.com, tangchen@cn.fujitsu.com,
tj@kernel.org, weiyang@linux.vnet.ibm.com,
mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] mm/memblock.c: fix NULL dereference error
Date: Tue, 2 Aug 2016 13:32:51 +0800 [thread overview]
Message-ID: <57A03083.7010003@zoho.com> (raw)
In-Reply-To: <201608021315.YmAh1zzr%fengguang.wu@intel.com>
i am sorry, the second patch is only a test patch, please don't apply it
i will send another mail for correct this
On 08/02/2016 01:23 PM, kbuild test robot wrote:
> Hi zijun_hu,
>
> [auto build test WARNING on mmotm/master]
> [also build test WARNING on v4.7 next-20160801]
> [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/zijun_hu/mm-memblock-c-fix-NULL-dereference-error/20160802-130708
> base: git://git.cmpxchg.org/linux-mmotm.git master
> config: i386-randconfig-x009-201631 (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/linux/kernel.h:13:0,
> from mm/memblock.c:13:
> mm/memblock.c: In function 'memblock_patch_verify':
>>> mm/memblock.c:1713:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 3 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
>>> mm/memblock.c:1713:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1713:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
>>> mm/memblock.c:1713:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1719:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 3 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
> mm/memblock.c:1719:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1719:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
> mm/memblock.c:1719:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1726:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 3 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
> mm/memblock.c:1726:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1726:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
> mm/memblock.c:1726:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
>
> vim +1713 mm/memblock.c
>
> 1697 pr_info(" memory size = %#llx reserved size = %#llx\n",
> 1698 (unsigned long long)memblock.memory.total_size,
> 1699 (unsigned long long)memblock.reserved.total_size);
> 1700
> 1701 memblock_dump(&memblock.memory, "memory");
> 1702 memblock_dump(&memblock.reserved, "reserved");
> 1703 }
> 1704
> 1705 void __init_memblock memblock_patch_verify(void)
> 1706 {
> 1707 u64 i;
> 1708 phys_addr_t this_start, this_end;
> 1709
> 1710 pr_info("in %s: memory\n", __func__);
> 1711 for_each_mem_range_rev(i, &memblock.memory, NULL, NUMA_NO_NODE,
> 1712 MEMBLOCK_NONE, &this_start, &this_end, NULL)
>> 1713 pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> 1714 i, this_start, this_end);
> 1715
> 1716 pr_info("in %s: reserved\n", __func__);
> 1717 for_each_mem_range_rev(i, &memblock.reserved, NULL, NUMA_NO_NODE,
> 1718 MEMBLOCK_NONE, &this_start, &this_end, NULL)
> 1719 pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> 1720 i, this_start, this_end);
> 1721
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: zijun_hu <zijun_hu@zoho.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org,
ard.biesheuvel@linaro.org, david@gibson.dropbear.id.au,
dev@g0hl1n.net, kuleshovmail@gmail.com, tangchen@cn.fujitsu.com,
tj@kernel.org, weiyang@linux.vnet.ibm.com,
mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] mm/memblock.c: fix NULL dereference error
Date: Tue, 2 Aug 2016 13:32:51 +0800 [thread overview]
Message-ID: <57A03083.7010003@zoho.com> (raw)
In-Reply-To: <201608021315.YmAh1zzr%fengguang.wu@intel.com>
i am sorry, the second patch is only a test patch, please don't apply it
i will send another mail for correct this
On 08/02/2016 01:23 PM, kbuild test robot wrote:
> Hi zijun_hu,
>
> [auto build test WARNING on mmotm/master]
> [also build test WARNING on v4.7 next-20160801]
> [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/zijun_hu/mm-memblock-c-fix-NULL-dereference-error/20160802-130708
> base: git://git.cmpxchg.org/linux-mmotm.git master
> config: i386-randconfig-x009-201631 (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/linux/kernel.h:13:0,
> from mm/memblock.c:13:
> mm/memblock.c: In function 'memblock_patch_verify':
>>> mm/memblock.c:1713:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 3 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
>>> mm/memblock.c:1713:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1713:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
>>> mm/memblock.c:1713:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1719:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 3 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
> mm/memblock.c:1719:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1719:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
> mm/memblock.c:1719:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1726:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 3 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
> mm/memblock.c:1726:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
> mm/memblock.c:1726:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type 'phys_addr_t {aka unsigned int}' [-Wformat=]
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^
> include/linux/printk.h:260:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^~~
> mm/memblock.c:1726:3: note: in expansion of macro 'pr_info'
> pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> ^~~~~~~
>
> vim +1713 mm/memblock.c
>
> 1697 pr_info(" memory size = %#llx reserved size = %#llx\n",
> 1698 (unsigned long long)memblock.memory.total_size,
> 1699 (unsigned long long)memblock.reserved.total_size);
> 1700
> 1701 memblock_dump(&memblock.memory, "memory");
> 1702 memblock_dump(&memblock.reserved, "reserved");
> 1703 }
> 1704
> 1705 void __init_memblock memblock_patch_verify(void)
> 1706 {
> 1707 u64 i;
> 1708 phys_addr_t this_start, this_end;
> 1709
> 1710 pr_info("in %s: memory\n", __func__);
> 1711 for_each_mem_range_rev(i, &memblock.memory, NULL, NUMA_NO_NODE,
> 1712 MEMBLOCK_NONE, &this_start, &this_end, NULL)
>> 1713 pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> 1714 i, this_start, this_end);
> 1715
> 1716 pr_info("in %s: reserved\n", __func__);
> 1717 for_each_mem_range_rev(i, &memblock.reserved, NULL, NUMA_NO_NODE,
> 1718 MEMBLOCK_NONE, &this_start, &this_end, NULL)
> 1719 pr_info("[%#016llx]\t[%#016llx-%#016llx]\n",
> 1720 i, this_start, this_end);
> 1721
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
next prev parent reply other threads:[~2016-08-02 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 5:03 [PATCH] mm/memblock.c: fix NULL dereference error zijun_hu
2016-08-02 5:03 ` zijun_hu
2016-08-02 5:20 ` zijun_hu
2016-08-02 5:20 ` zijun_hu
2016-08-02 5:23 ` kbuild test robot
2016-08-02 5:32 ` zijun_hu [this message]
2016-08-02 5:32 ` zijun_hu
2016-08-02 5:39 ` zijun_hu
2016-08-02 5:39 ` zijun_hu
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=57A03083.7010003@zoho.com \
--to=zijun_hu@zoho.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=dev@g0hl1n.net \
--cc=kbuild-all@01.org \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mm-commits@vger.kernel.org \
--cc=tangchen@cn.fujitsu.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=weiyang@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.