From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: lib/memcpy_kunit.c:299 init_large() warn: calling memset(x, y, ARRAY_SIZE());
Date: Mon, 11 Sep 2023 05:05:12 +0800 [thread overview]
Message-ID: <202309110524.wasJTGqB-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Kees Cook <keescook@chromium.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 1548b060d6f32a00a2f7e2c11328205fb66fc4fa
commit: 96fce387d58fa8eae6e8d9b1ecdfbc18292d7a68 kunit/memcpy: Add dynamic size and window tests
date: 11 months ago
:::::: branch date: 2 hours ago
:::::: commit date: 11 months ago
config: openrisc-randconfig-r071-20230906 (https://download.01.org/0day-ci/archive/20230911/202309110524.wasJTGqB-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230911/202309110524.wasJTGqB-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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202309110524.wasJTGqB-lkp@intel.com/
smatch warnings:
lib/memcpy_kunit.c:299 init_large() warn: calling memset(x, y, ARRAY_SIZE());
vim +299 lib/memcpy_kunit.c
96fce387d58fa8 Kees Cook 2022-09-28 290
96fce387d58fa8 Kees Cook 2022-09-28 291 /* Get many bit patterns. */
96fce387d58fa8 Kees Cook 2022-09-28 292 get_random_bytes(large_src, ARRAY_SIZE(large_src));
96fce387d58fa8 Kees Cook 2022-09-28 293
96fce387d58fa8 Kees Cook 2022-09-28 294 /* Make sure we have non-zero edges. */
96fce387d58fa8 Kees Cook 2022-09-28 295 set_random_nonzero(test, &large_src[0]);
96fce387d58fa8 Kees Cook 2022-09-28 296 set_random_nonzero(test, &large_src[ARRAY_SIZE(large_src) - 1]);
96fce387d58fa8 Kees Cook 2022-09-28 297
96fce387d58fa8 Kees Cook 2022-09-28 298 /* Explicitly zero the entire destination. */
96fce387d58fa8 Kees Cook 2022-09-28 @299 memset(large_dst, 0, ARRAY_SIZE(large_dst));
96fce387d58fa8 Kees Cook 2022-09-28 300 }
96fce387d58fa8 Kees Cook 2022-09-28 301
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-09-10 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 21:05 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-08 20:56 lib/memcpy_kunit.c:299 init_large() warn: calling memset(x, y, ARRAY_SIZE()); kernel test robot
2022-12-31 11:51 kernel test robot
2023-01-03 7:58 ` Dan Carpenter
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=202309110524.wasJTGqB-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.