From: kernel test robot <lkp@intel.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: [rcu:dev.2020.11.06a 15/22] kernel/taskstats.c:350: undefined reference to `cpulist_parse'
Date: Tue, 10 Nov 2020 16:02:26 +0800 [thread overview]
Message-ID: <202011101616.8jVLK4mG-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3385 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.11.06a
head: 5cec02881428f10c4a1632c3aebb666b12888958
commit: 015465e505581b068dba346e6e73caeb673e8753 [15/22] cpumask: un-inline cpulist_parse; prepare for ascii helpers
config: h8300-randconfig-r013-20201109 (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?id=015465e505581b068dba346e6e73caeb673e8753
git remote add rcu https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
git fetch --no-tags rcu dev.2020.11.06a
git checkout 015465e505581b068dba346e6e73caeb673e8753
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
h8300-linux-ld: arch/h8300/kernel/entry.o: in function `resume_kernel':
arch/h8300/kernel/entry.S:324: undefined reference to `TI_PRE_COUNT'
h8300-linux-ld: kernel/taskstats.o: in function `parse':
>> kernel/taskstats.c:350: undefined reference to `cpulist_parse'
vim +350 kernel/taskstats.c
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 332
41c7bb9588904eb Rusty Russell 2009-01-01 333 static int parse(struct nlattr *na, struct cpumask *mask)
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 334 {
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 335 char *data;
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 336 int len;
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 337 int ret;
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 338
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 339 if (na == NULL)
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 340 return 1;
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 341 len = nla_len(na);
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 342 if (len > TASKSTATS_CPUMASK_MAXLEN)
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 343 return -E2BIG;
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 344 if (len < 1)
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 345 return -EINVAL;
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 346 data = kmalloc(len, GFP_KERNEL);
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 347 if (!data)
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 348 return -ENOMEM;
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 349 nla_strlcpy(data, na, len);
29c0177e6a4ac09 Rusty Russell 2008-12-13 @350 ret = cpulist_parse(data, mask);
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 351 kfree(data);
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 352 return ret;
f9fd8914c1acca0 Shailabh Nagar 2006-07-14 353 }
ad4ecbcba72855a Shailabh Nagar 2006-07-14 354
:::::: The code at line 350 was first introduced by commit
:::::: 29c0177e6a4ac094302bed54a1d4bbb6b740a9ef cpumask: change cpumask_scnprintf, cpumask_parse_user, cpulist_parse, and cpulist_scnprintf to take pointers.
:::::: TO: Rusty Russell <rusty@rustcorp.com.au>
:::::: CC: Rusty Russell <rusty@rustcorp.com.au>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24049 bytes --]
reply other threads:[~2020-11-10 8:03 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=202011101616.8jVLK4mG-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@kernel.org \
/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®