From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <lkp@intel.com>
Cc: "Daniel, Axtens," <dja@axtens.net>,
kbuild-all@lists.01.org, Johannes Weiner <hannes@cmpxchg.org>,
Dmitry Vyukov <dvyukov@google.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [hnaz-linux-mm:master 169/698] include/linux/string.h:307:9: note: in expansion of macro '__underlying_strncpy'
Date: Mon, 1 Jun 2020 18:04:55 -0700 [thread overview]
Message-ID: <20200601180455.1a2f38368da33c7a0bb8d6fb@linux-foundation.org> (raw)
In-Reply-To: <202005301819.G4uARaFJ%lkp@intel.com>
On Sat, 30 May 2020 18:07:21 +0800 kbuild test robot <lkp@intel.com> wrote:
> tree: https://github.com/hnaz/linux-mm master
> head: a085ccd0a3e9741df5fe3a0e54228dc033759169
> commit: e7c89f2e1992cc557c934608cc27e2b9759cb21a [169/698] string.h: fix incompatibility between FORTIFY_SOURCE and KASAN
> config: arm-aspeed_g5_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
> 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
> git checkout e7c89f2e1992cc557c934608cc27e2b9759cb21a
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
>
> from include/linux/pid.h:5,
> from include/linux/sched.h:14,
> from include/linux/ratelimit.h:6,
> from include/linux/dev_printk.h:16,
> from include/linux/device.h:15,
> from include/linux/hdmi.h:28,
> from drivers/video/hdmi.c:28:
> In function 'strncpy',
> inlined from 'hdmi_spd_infoframe_init' at drivers/video/hdmi.c:230:2:
> include/linux/string.h:297:30: warning: '__builtin_strncpy' specified bound 8 equals destination size [-Wstringop-truncation]
> 297 | #define __underlying_strncpy __builtin_strncpy
> | ^
> >> include/linux/string.h:307:9: note: in expansion of macro '__underlying_strncpy'
> 307 | return __underlying_strncpy(p, q, size);
> | ^~~~~~~~~~~~~~~~~~~~
Looks like another false positive.
Daniel, is there a practical way of suppressing these?
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild-all@lists.01.org
Subject: Re: [hnaz-linux-mm:master 169/698] include/linux/string.h:307:9: note: in expansion of macro '__underlying_strncpy'
Date: Mon, 01 Jun 2020 18:04:55 -0700 [thread overview]
Message-ID: <20200601180455.1a2f38368da33c7a0bb8d6fb@linux-foundation.org> (raw)
In-Reply-To: <202005301819.G4uARaFJ%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
On Sat, 30 May 2020 18:07:21 +0800 kbuild test robot <lkp@intel.com> wrote:
> tree: https://github.com/hnaz/linux-mm master
> head: a085ccd0a3e9741df5fe3a0e54228dc033759169
> commit: e7c89f2e1992cc557c934608cc27e2b9759cb21a [169/698] string.h: fix incompatibility between FORTIFY_SOURCE and KASAN
> config: arm-aspeed_g5_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
> 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
> git checkout e7c89f2e1992cc557c934608cc27e2b9759cb21a
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
>
> from include/linux/pid.h:5,
> from include/linux/sched.h:14,
> from include/linux/ratelimit.h:6,
> from include/linux/dev_printk.h:16,
> from include/linux/device.h:15,
> from include/linux/hdmi.h:28,
> from drivers/video/hdmi.c:28:
> In function 'strncpy',
> inlined from 'hdmi_spd_infoframe_init' at drivers/video/hdmi.c:230:2:
> include/linux/string.h:297:30: warning: '__builtin_strncpy' specified bound 8 equals destination size [-Wstringop-truncation]
> 297 | #define __underlying_strncpy __builtin_strncpy
> | ^
> >> include/linux/string.h:307:9: note: in expansion of macro '__underlying_strncpy'
> 307 | return __underlying_strncpy(p, q, size);
> | ^~~~~~~~~~~~~~~~~~~~
Looks like another false positive.
Daniel, is there a practical way of suppressing these?
Thanks.
next prev parent reply other threads:[~2020-06-02 1:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 10:07 [hnaz-linux-mm:master 169/698] include/linux/string.h:307:9: note: in expansion of macro '__underlying_strncpy' kbuild test robot
2020-05-30 10:07 ` kbuild test robot
2020-06-02 1:04 ` Andrew Morton [this message]
2020-06-02 1:04 ` Andrew Morton
2020-06-02 3:26 ` Daniel Axtens
2020-06-02 3:26 ` Daniel Axtens
2020-06-02 3:53 ` Daniel Axtens
2020-06-02 3:53 ` Daniel Axtens
2020-06-02 5:55 ` Daniel Axtens
2020-06-02 5:55 ` Daniel Axtens
2020-06-02 19:16 ` Andrew Morton
2020-06-02 19:16 ` Andrew Morton
2020-06-05 10:35 ` Daniel Axtens
2020-06-05 10:35 ` Daniel Axtens
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=20200601180455.1a2f38368da33c7a0bb8d6fb@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dja@axtens.net \
--cc=dvyukov@google.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
/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.