From: kernel test robot <lkp@intel.com>
To: Peter Collingbourne <pcc@google.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: mm/kasan/sw_tags.c:211:6: warning: no previous prototype for function 'kasan_tag_mismatch'
Date: Tue, 8 Mar 2022 22:37:45 +0800 [thread overview]
Message-ID: <202203082234.bp7VLzQE-lkp@intel.com> (raw)
Hi Peter,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ea4424be16887a37735d6550cfd0611528dbe5d9
commit: 1cbdf60bd1b74e397d48aa877367cfc621f45ffe kasan: arm64: support specialized outlined tag mismatch checks
date: 10 months ago
config: arm64-randconfig-r023-20220307 (https://download.01.org/0day-ci/archive/20220308/202203082234.bp7VLzQE-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project d271fc04d5b97b12e6b797c6067d3c96a8d7470e)
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 arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1cbdf60bd1b74e397d48aa877367cfc621f45ffe
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 1cbdf60bd1b74e397d48aa877367cfc621f45ffe
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash mm/kasan/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> mm/kasan/sw_tags.c:211:6: warning: no previous prototype for function 'kasan_tag_mismatch' [-Wmissing-prototypes]
void kasan_tag_mismatch(unsigned long addr, unsigned long access_info,
^
mm/kasan/sw_tags.c:211:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void kasan_tag_mismatch(unsigned long addr, unsigned long access_info,
^
static
1 warning generated.
vim +/kasan_tag_mismatch +211 mm/kasan/sw_tags.c
210
> 211 void kasan_tag_mismatch(unsigned long addr, unsigned long access_info,
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-03-08 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 14:37 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-01 12:51 mm/kasan/sw_tags.c:211:6: warning: no previous prototype for function 'kasan_tag_mismatch' kernel test robot
2022-07-12 15:50 kernel test robot
2022-05-09 11:47 kernel test robot
2022-04-21 20:25 kernel test robot
2022-02-26 23:09 kernel test robot
2022-01-07 9:00 kernel test robot
2022-01-07 9:00 ` kernel test robot
2021-12-22 12:19 kernel test robot
2021-12-22 12:19 ` kernel test robot
2021-11-26 12:28 kernel test robot
2021-11-26 12:28 ` kernel test robot
2021-11-16 20:43 kernel test robot
2021-11-16 20:43 ` kernel test robot
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=202203082234.bp7VLzQE-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=pcc@google.com \
--cc=will@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 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.