From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [kees:kspp/memcpy/next-20210618/v0 58/82] lib/string_helpers.c:883:6: warning: no previous prototype for function '__read_overflow2_field'
Date: Sat, 19 Jun 2021 21:28:45 +0800 [thread overview]
Message-ID: <202106192143.O2Ok48mo-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3731 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git kspp/memcpy/next-20210618/v0
head: fd2aa2a169de8bde9502e7a2fc48cd03d4bfd996
commit: 21405e341f4b8742f8c6d8b91ad39348d7cf970f [58/82] fortify: Detect struct member overflows in memcpy()
config: powerpc64-randconfig-r004-20210618 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project d1baf2895467735ab14f4b3415fce204c0cc8e7f)
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://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=21405e341f4b8742f8c6d8b91ad39348d7cf970f
git remote add kees https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
git fetch --no-tags kees kspp/memcpy/next-20210618/v0
git checkout 21405e341f4b8742f8c6d8b91ad39348d7cf970f
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=powerpc64
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 >>):
>> lib/string_helpers.c:883:6: warning: no previous prototype for function '__read_overflow2_field' [-Wmissing-prototypes]
void __read_overflow2_field(void) { }
^
lib/string_helpers.c:883:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void __read_overflow2_field(void) { }
^
static
>> lib/string_helpers.c:885:6: warning: no previous prototype for function '__write_overflow_field' [-Wmissing-prototypes]
void __write_overflow_field(void) { }
^
lib/string_helpers.c:885:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void __write_overflow_field(void) { }
^
static
>> lib/string_helpers.c:889:6: warning: no previous prototype for function 'fortify_warn_write' [-Wmissing-prototypes]
void fortify_warn_write(const char *func, size_t buffer_size, size_t write_size)
^
lib/string_helpers.c:889:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void fortify_warn_write(const char *func, size_t buffer_size, size_t write_size)
^
static
lib/string_helpers.c:896:6: warning: no previous prototype for function 'fortify_panic' [-Wmissing-prototypes]
void fortify_panic(const char *name)
^
lib/string_helpers.c:896:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void fortify_panic(const char *name)
^
static
4 warnings generated.
vim +/__read_overflow2_field +883 lib/string_helpers.c
881
882 /* These are placeholders for fortify compile-time warnings. */
> 883 void __read_overflow2_field(void) { }
884 EXPORT_SYMBOL(__read_overflow2_field);
> 885 void __write_overflow_field(void) { }
886 EXPORT_SYMBOL(__write_overflow_field);
887
888 /* Run-time warnings */
> 889 void fortify_warn_write(const char *func, size_t buffer_size, size_t write_size)
890 {
891 WARN_ONCE(1, "%s: detected buffer (size %zu) overflowing write (size %zu)\n",
892 func, buffer_size, write_size);
893 }
894 EXPORT_SYMBOL(fortify_warn_write);
895
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 24270 bytes --]
reply other threads:[~2021-06-19 13:28 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=202106192143.O2Ok48mo-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.