From: kbuild test robot <lkp@intel.com>
To: zhong jiang <zhongjiang@huawei.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org, mhocko@suse.com,
pasha.tatashin@oracle.com, dan.j.williams@intel.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Use BUG_ON directly instead of a if condition followed by BUG
Date: Tue, 11 Sep 2018 03:54:11 +0800 [thread overview]
Message-ID: <201809110356.FSz0iqpq%fengguang.wu@intel.com> (raw)
In-Reply-To: <1536588197-22115-1-git-send-email-zhongjiang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]
Hi zhong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc3 next-20180910]
[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/zhong-jiang/mm-Use-BUG_ON-directly-instead-of-a-if-condition-followed-by-BUG/20180911-025008
config: x86_64-randconfig-x012-201836 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
mm/memory_hotplug.c: In function 'remove_memory':
>> mm/memory_hotplug.c:1891:9: error: macro "BUG" passed 1 arguments, but takes just 0
BUG(ret);
^
>> mm/memory_hotplug.c:1891:2: error: 'BUG' undeclared (first use in this function)
BUG(ret);
^~~
mm/memory_hotplug.c:1891:2: note: each undeclared identifier is reported only once for each function it appears in
vim +/BUG +1891 mm/memory_hotplug.c
1865
1866 /**
1867 * remove_memory
1868 * @nid: the node ID
1869 * @start: physical address of the region to remove
1870 * @size: size of the region to remove
1871 *
1872 * NOTE: The caller must call lock_device_hotplug() to serialize hotplug
1873 * and online/offline operations before this call, as required by
1874 * try_offline_node().
1875 */
1876 void __ref remove_memory(int nid, u64 start, u64 size)
1877 {
1878 int ret;
1879
1880 BUG_ON(check_hotplug_memory_range(start, size));
1881
1882 mem_hotplug_begin();
1883
1884 /*
1885 * All memory blocks must be offlined before removing memory. Check
1886 * whether all memory blocks in question are offline and trigger a BUG()
1887 * if this is not the case.
1888 */
1889 ret = walk_memory_range(PFN_DOWN(start), PFN_UP(start + size - 1), NULL,
1890 check_memblock_offlined_cb);
> 1891 BUG(ret);
---
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: 31308 bytes --]
prev parent reply other threads:[~2018-09-10 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 14:03 zhong jiang
2018-09-10 14:27 ` Michal Hocko
2018-09-10 19:54 ` kbuild test robot [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=201809110356.FSz0iqpq%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pasha.tatashin@oracle.com \
--cc=zhongjiang@huawei.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