From: Philip Li <philip.li@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>, <oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [linux-next:master 10401/13390] include/linux/fortify-string.h:65:29: warning: '__builtin_strcpy' source argument is the same as destination
Date: Thu, 31 Aug 2023 10:08:35 +0800 [thread overview]
Message-ID: <ZO/2I1SHFlEQR64P@rli9-mobl> (raw)
In-Reply-To: <202308301542.li3KHkJl-lkp@intel.com>
On Wed, Aug 30, 2023 at 03:18:34PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 56585460cc2ec44fc5d66924f0a116f57080f0dc
> commit: 26030cb984dd65e0cb2d0c2489d94941cf8897b4 [10401/13390] extrawarn: move -Wrestrict into W=1 warnings
> config: um-randconfig-r034-20230830 (https://download.01.org/0day-ci/archive/20230830/202308301542.li3KHkJl-lkp@intel.com/config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230830/202308301542.li3KHkJl-lkp@intel.com/reproduce)
Sorry for the wrong report, kindly ignore this
>
> 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/202308301542.li3KHkJl-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/linux/string.h:254,
> from include/linux/bitmap.h:11,
> from include/linux/cpumask.h:12,
> from include/linux/mm_types_task.h:14,
> from include/linux/mm_types.h:5,
> from include/linux/buildid.h:5,
> from include/linux/kallsyms.h:10,
> from kernel/kallsyms.c:15:
> kernel/kallsyms.c: In function '__sprint_symbol.isra.0':
> >> include/linux/fortify-string.h:65:29: warning: '__builtin_strcpy' source argument is the same as destination [-Wrestrict]
> 65 | #define __underlying_strcpy __builtin_strcpy
> | ^
> include/linux/fortify-string.h:794:10: note: in expansion of macro '__underlying_strcpy'
> 794 | return __underlying_strcpy(p, q);
> | ^~~~~~~~~~~~~~~~~~~
>
>
> vim +/__builtin_strcpy +65 include/linux/fortify-string.h
>
> 78a498c3a227f2 Alexander Potapenko 2022-10-24 61
> 78a498c3a227f2 Alexander Potapenko 2022-10-24 62 #define __underlying_memchr __builtin_memchr
> 78a498c3a227f2 Alexander Potapenko 2022-10-24 63 #define __underlying_memcmp __builtin_memcmp
> a28a6e860c6cf2 Francis Laniel 2021-02-25 64 #define __underlying_strcat __builtin_strcat
> a28a6e860c6cf2 Francis Laniel 2021-02-25 @65 #define __underlying_strcpy __builtin_strcpy
> a28a6e860c6cf2 Francis Laniel 2021-02-25 66 #define __underlying_strlen __builtin_strlen
> a28a6e860c6cf2 Francis Laniel 2021-02-25 67 #define __underlying_strncat __builtin_strncat
> a28a6e860c6cf2 Francis Laniel 2021-02-25 68 #define __underlying_strncpy __builtin_strncpy
> a28a6e860c6cf2 Francis Laniel 2021-02-25 69 #endif
> a28a6e860c6cf2 Francis Laniel 2021-02-25 70
>
> :::::: The code at line 65 was first introduced by commit
> :::::: a28a6e860c6cf231cf3c5171c75c342adcd00406 string.h: move fortified functions definitions in a dedicated header.
>
> :::::: TO: Francis Laniel <laniel_francis@privacyrequired.com>
> :::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
prev parent reply other threads:[~2023-08-31 2:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 7:18 kernel test robot
2023-08-31 2:08 ` Philip Li [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=ZO/2I1SHFlEQR64P@rli9-mobl \
--to=philip.li@intel.com \
--cc=arnd@arndb.de \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox