From: kbuild test robot <lkp@intel.com>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Michael Bringmann <mwb@linux.vnet.ibm.com>,
John Allen <jallen@linux.vnet.ibm.com>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
9e5050e1-e0cc-0e0e-7b31-5dcb38b307f4@linux.vnet.ibm.com
Subject: Re: [PATCH V9 2/2] powerpc/nodes: Ensure enough nodes avail for operations
Date: Thu, 24 Aug 2017 00:04:10 +0800 [thread overview]
Message-ID: <201708232344.6sC93aF6%fengguang.wu@intel.com> (raw)
In-Reply-To: <83b05ed2-8d18-3d5c-2003-b022d0d55eb2@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2977 bytes --]
Hi Michael,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.13-rc6 next-20170823]
[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/Michael-Bringmann/powerpc-numa-Update-CPU-topology-when-VPHN-enabled/20170823-173526
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-defconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=powerpc
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All errors (new ones prefixed by >>):
arch/powerpc/mm/numa.c: In function 'initmem_init':
>> arch/powerpc/mm/numa.c:923:3: error: 'levelval' may be used uninitialized in this function [-Werror=maybe-uninitialized]
printk(KERN_INFO "Numa nodes avail: %d (%d) \n", (int) levelval, (int) entries);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/powerpc/mm/numa.c:904:21: note: 'levelval' was declared here
u32 len, entries, levelval, i;
^~~~~~~~
cc1: all warnings being treated as errors
vim +/levelval +923 arch/powerpc/mm/numa.c
895
896 static void __init node_associativity_setup(void)
897 {
898 struct device_node *rtas;
899 printk(KERN_INFO "%s:%d\n", __FUNCTION__, __LINE__);
900
901 rtas = of_find_node_by_path("/rtas");
902 if (rtas) {
903 const __be32 *prop;
904 u32 len, entries, levelval, i;
905 printk(KERN_INFO "%s:%d\n", __FUNCTION__, __LINE__);
906
907 prop = of_get_property(rtas, "ibm,max-associativity-domains", &len);
908 if (!prop || len < sizeof(unsigned int)) {
909 printk(KERN_INFO "%s:%d\n", __FUNCTION__, __LINE__);
910 goto endit;
911 }
912
913 entries = of_read_number(prop++, 1);
914
915 if (len < (entries * sizeof(unsigned int))) {
916 printk(KERN_INFO "%s:%d\n", __FUNCTION__, __LINE__);
917 goto endit;
918 }
919
920 for (i = 0; i < entries; i++)
921 levelval = of_read_number(prop++, 1);
922
> 923 printk(KERN_INFO "Numa nodes avail: %d (%d) \n", (int) levelval, (int) entries);
924
925 for (i = 0; i < levelval; i++) {
926 if (!node_possible(i)) {
927 setup_node_data(i, 0, 0);
928 node_set(i, node_possible_map);
929 }
930 }
931 }
932
933 endit:
934 if (rtas)
935 of_node_put(rtas);
936 }
937
---
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: 23572 bytes --]
prev parent reply other threads:[~2017-08-23 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 21:44 Michael Bringmann
2017-08-23 11:20 ` Michael Ellerman
2017-08-23 14:42 ` Nathan Fontenot
2017-08-23 16:04 ` 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=201708232344.6sC93aF6%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=9e5050e1-e0cc-0e0e-7b31-5dcb38b307f4@linux.vnet.ibm.com \
--cc=jallen@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=mwb@linux.vnet.ibm.com \
--cc=nfont@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®