From: kernel test robot <lkp@intel.com>
To: Matthew Maurer <mmaurer@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Miguel Ojeda <ojeda@kernel.org>,
Andrey Konovalov <andreyknvl@gmail.com>
Subject: [linux-next:master 11937/12481] mm/kasan/kasan_test_c.c:48:6: sparse: sparse: symbol 'kasan_ptr_result' was not declared. Should it be static?
Date: Fri, 20 Sep 2024 18:38:57 +0800 [thread overview]
Message-ID: <202409201822.CVGhLWKs-lkp@intel.com> (raw)
Hi Matthew,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 62f92d634458a1e308bb699986b9147a6d670457
commit: a2f11547052001bd448ccec81dd1e68409078fbb [11937/12481] kasan: rust: Add KASAN smoke test via UAF
config: x86_64-randconfig-123-20240920 (https://download.01.org/0day-ci/archive/20240920/202409201822.CVGhLWKs-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240920/202409201822.CVGhLWKs-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/202409201822.CVGhLWKs-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/kasan/kasan_test_c.c:48:6: sparse: sparse: symbol 'kasan_ptr_result' was not declared. Should it be static?
>> mm/kasan/kasan_test_c.c:49:5: sparse: sparse: symbol 'kasan_int_result' was not declared. Should it be static?
vim +/kasan_ptr_result +48 mm/kasan/kasan_test_c.c
7ce0ea19d50e4e mm/kasan/kasan_test.c Andrey Konovalov 2022-09-27 43
adb72ae1915db2 lib/test_kasan.c Daniel Axtens 2020-06-03 44 /*
0fd379253691e7 lib/test_kasan.c Andrey Konovalov 2021-02-24 45 * Some tests use these global variables to store return values from function
0fd379253691e7 lib/test_kasan.c Andrey Konovalov 2021-02-24 46 * calls that could otherwise be eliminated by the compiler as dead code.
adb72ae1915db2 lib/test_kasan.c Daniel Axtens 2020-06-03 47 */
adb72ae1915db2 lib/test_kasan.c Daniel Axtens 2020-06-03 @48 void *kasan_ptr_result;
83c4e7a0363bdb lib/test_kasan.c Patricia Alfonso 2020-10-13 @49 int kasan_int_result;
83c4e7a0363bdb lib/test_kasan.c Patricia Alfonso 2020-10-13 50
:::::: The code at line 48 was first introduced by commit
:::::: adb72ae1915db28f934e9e02c18bfcea2f3ed3b7 kasan: stop tests being eliminated as dead code with FORTIFY_SOURCE
:::::: TO: Daniel Axtens <dja@axtens.net>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-09-20 10:39 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=202409201822.CVGhLWKs-lkp@intel.com \
--to=lkp@intel.com \
--cc=andreyknvl@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mmaurer@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@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