On Sat, 30 May 2020 18:07:21 +0800 kbuild test robot <lkp@xxxxxxxxx> 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.
