From: kernel test robot <lkp@intel.com>
To: "José Aquiles Guedes de Rezende" <jjoseaquiless@gmail.com>,
"Jiri Pirko" <jiri@nvidia.com>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
brendanhiggins@google.com, dlatypov@google.com,
davidgow@google.com, linux-kselftest@vger.kernel.org,
~lkcamp/patches@lists.sr.ht,
"José Aquiles Guedes de Rezende" <jjoseaquiless@gmail.com>,
"Matheus Henrique de Souza Silva"
<matheushenriquedesouzasilva@protonmail.com>
Subject: Re: [PATCH] lib: use of kunit in test_parman.c
Date: Wed, 28 Jul 2021 12:46:26 +0800 [thread overview]
Message-ID: <202107281259.okaHKmZt-lkp@intel.com> (raw)
In-Reply-To: <20210727225847.22185-1-jjoseaquiless@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2939 bytes --]
Hi "José,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on ipvs/master]
[also build test ERROR on linux/master linus/master v5.14-rc3 next-20210727]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Jos-Aquiles-Guedes-de-Rezende/lib-use-of-kunit-in-test_parman-c/20210728-070506
base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs.git master
config: powerpc64-buildonly-randconfig-r006-20210727 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project c49df15c278857adecd12db6bb1cdc96885f7079)
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
# install powerpc64 cross compiling tool for clang build
# apt-get install binutils-powerpc64-linux-gnu
# https://github.com/0day-ci/linux/commit/28790f5c89e89dc96adf7bd4c748ddd505a52391
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Jos-Aquiles-Guedes-de-Rezende/lib-use-of-kunit-in-test_parman-c/20210728-070506
git checkout 28790f5c89e89dc96adf7bd4c748ddd505a52391
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=powerpc SHELL=/bin/bash
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 >>):
>> lib/test_parman.c:96:32: error: no member named 'kunit_test' in 'struct task_struct'
struct kunit *test = current->kunit_test;
~~~~~~~ ^
1 error generated.
vim +96 lib/test_parman.c
93
94 static int test_parman_resize(void *priv, unsigned long new_count)
95 {
> 96 struct kunit *test = current->kunit_test;
97 struct test_parman *test_parman = priv;
98 struct test_parman_item **prio_array;
99 unsigned long old_count;
100
101 prio_array = krealloc(test_parman->prio_array,
102 ITEM_PTRS_SIZE(new_count), GFP_KERNEL);
103 KUNIT_EXPECT_NOT_ERR_OR_NULL(test, prio_array);
104 if (new_count == 0)
105 return 0;
106 if (!prio_array)
107 return -ENOMEM;
108 old_count = test_parman->prio_array_limit;
109 if (new_count > old_count)
110 memset(&prio_array[old_count], 0,
111 ITEM_PTRS_SIZE(new_count - old_count));
112 test_parman->prio_array = prio_array;
113 test_parman->prio_array_limit = new_count;
114 return 0;
115 }
116
---
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: 41642 bytes --]
prev parent reply other threads:[~2021-07-28 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 22:58 [PATCH] lib: use of kunit in test_parman.c José Aquiles Guedes de Rezende
2021-07-28 0:04 ` Daniel Latypov
2021-07-28 1:37 ` David Gow
2021-07-28 4:46 ` kernel 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=202107281259.okaHKmZt-lkp@intel.com \
--to=lkp@intel.com \
--cc=brendanhiggins@google.com \
--cc=clang-built-linux@googlegroups.com \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=jiri@nvidia.com \
--cc=jjoseaquiless@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matheushenriquedesouzasilva@protonmail.com \
--cc=netdev@vger.kernel.org \
--cc=~lkcamp/patches@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).