From: kernel test robot <lkp@intel.com>
To: Tamir Duberstein <tamird@kernel.org>,
David Gow <davidgow@google.com>,
John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Naveen N Rao <naveen@kernel.org>,
Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Shuah Khan <skhan@linuxfoundation.org>,
Kees Cook <kees@kernel.org>,
Christophe Leroy <chleroy@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linuxppc-dev@lists.ozlabs.org, linux-kselftest@vger.kernel.org,
Tamir Duberstein <tamird@gmail.com>
Subject: Re: [PATCH v2 3/3] bitmap: break kunit into test cases
Date: Tue, 23 Dec 2025 22:18:06 +0800 [thread overview]
Message-ID: <202512232235.vUHmJH7T-lkp@intel.com> (raw)
In-Reply-To: <20251222-bitmap-kunit-convert-v2-3-6a61a5330eff@gmail.com>
Hi Tamir,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8f0b4cce4481fb22653697cced8d0d04027cb1e8]
url: https://github.com/intel-lab-lkp/linux/commits/Tamir-Duberstein/test_bitmap-extract-benchmark-module/20251222-214306
base: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
patch link: https://lore.kernel.org/r/20251222-bitmap-kunit-convert-v2-3-6a61a5330eff%40gmail.com
patch subject: [PATCH v2 3/3] bitmap: break kunit into test cases
config: arm64-randconfig-004-20251223 (https://download.01.org/0day-ci/archive/20251223/202512232235.vUHmJH7T-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251223/202512232235.vUHmJH7T-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202512232235.vUHmJH7T-lkp@intel.com/
All warnings (new ones prefixed by >>):
lib/bitmap_kunit.c: In function 'test_bitmap_printlist':
>> lib/bitmap_kunit.c:468:2: warning: 'memset' used with length equal to number of elements without multiplication by element size [-Wmemset-elt-size]
468 | memset(bmap, -1, PAGE_SIZE);
| ^~~~~~
vim +/memset +468 lib/bitmap_kunit.c
6ea86bdfc169ba lib/test_bitmap.c Yury Norov 2019-05-14 459
8ef3340af7139f lib/bitmap_kunit.c Tamir Duberstein 2025-12-22 460 static void test_bitmap_printlist(struct kunit *kunittest)
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 461 {
8ef3340af7139f lib/bitmap_kunit.c Tamir Duberstein 2025-12-22 462 static long bmap[PAGE_SIZE];
8ef3340af7139f lib/bitmap_kunit.c Tamir Duberstein 2025-12-22 463 static char buf[PAGE_SIZE];
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 464 char expected[256];
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 465 int ret, slen;
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 466 ktime_t time;
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 467
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 @468 memset(bmap, -1, PAGE_SIZE);
8ef3340af7139f lib/bitmap_kunit.c Tamir Duberstein 2025-12-22 469 slen = snprintf(expected, sizeof(expected), "0-%ld\n", PAGE_SIZE * 8 - 1);
8ef3340af7139f lib/bitmap_kunit.c Tamir Duberstein 2025-12-22 470 KUNIT_ASSERT_GT(kunittest, slen, 0);
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 471
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 472 time = ktime_get();
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 473 ret = bitmap_print_to_pagebuf(true, buf, bmap, PAGE_SIZE * 8);
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 474 time = ktime_get() - time;
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 475
8ef3340af7139f lib/bitmap_kunit.c Tamir Duberstein 2025-12-22 476 KUNIT_ASSERT_EQ(kunittest, ret, slen);
8ef3340af7139f lib/bitmap_kunit.c Tamir Duberstein 2025-12-22 477 KUNIT_ASSERT_STREQ(kunittest, buf, expected);
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 478
8ef3340af7139f lib/bitmap_kunit.c Tamir Duberstein 2025-12-22 479 kunit_info(kunittest, "Time: %llu", time);
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 480 }
db7313005e9c2d lib/test_bitmap.c Yury Norov 2021-08-14 481
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-12-23 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251222-bitmap-kunit-convert-v2-3-6a61a5330eff@gmail.com>
2025-12-23 13:22 ` kernel test robot
2025-12-23 14:18 ` 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=202512232235.vUHmJH7T-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=chleroy@kernel.org \
--cc=davidgow@google.com \
--cc=geert@linux-m68k.org \
--cc=jhubbard@nvidia.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=tamird@gmail.com \
--cc=tamird@kernel.org \
--cc=usama.anjum@collabora.com \
--cc=yury.norov@gmail.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