[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d8fd6210-84eb-6d32-6486-1d90c86186ca@embeddedor.com>
Date: Mon, 21 Aug 2023 11:26:17 -0600
From: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To: kernel test robot <lkp@...el.com>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
"Liu, Yujie" <yujie.liu@...el.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [gustavoars:testing/fam01-next20230817] BUILD SUCCESS WITH
WARNING dbd3e479335bc8b09ea540102109ac38b0a73336
Hi there!
It'd be great to add to these reports the versions of the compilers you are using
to build the kernel.
It's not uncommon that some compiler versions contain bugs. And in cases where kernel
developers are aware of those issues, knowing the exact version used to build the
kernel will help us determine whether the issues reported may be false positives or
not.
Maybe just one line at the beginning mentioning the versions:
`GCC 13.2.0 and Clang 16.0.0 builds`
Thank you!
--
Gustavo
On 8/18/23 01:55, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git testing/fam01-next20230817
> branch HEAD: dbd3e479335bc8b09ea540102109ac38b0a73336 net: sched: cls_u32: Fix allocation in u32_init()
>
> Warning: (recently discovered and may have been fixed)
>
> arch/arc/include/asm/io.h:129:9: warning: array subscript 0 is outside array bounds of 'volatile void[0]' [-Warray-bounds]
> arch/loongarch/include/asm/atomic.h:174:9: warning: array subscript 1 is outside array bounds of 'struct cpumask[1]' [-Warray-bounds]
> arch/sparc/include/asm/string.h:15:25: warning: '__builtin_memcpy' forming offset [132, 257] is out of the bounds [0, 132] of object 'send_data' with type 'u8[132]' {aka 'unsigned char[132]'} [-Warray-bounds]
> include/asm-generic/unaligned.h:14:15: warning: array subscript -1 is outside array bounds of 'unsigned char[2147483647]' [-Warray-bounds]
> lib/vsprintf.c:2893:33: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
> mm/mempolicy.c:3117:26: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
>
> Warning ids grouped by kconfigs:
>
> gcc_recent_errors
> |-- arc-allyesconfig
> | `-- arch-arc-include-asm-io.h:warning:array-subscript-is-outside-array-bounds-of-volatile-void
> |-- arc-randconfig-r043-20230818
> | `-- arch-arc-include-asm-io.h:warning:array-subscript-is-outside-array-bounds-of-volatile-void
> |-- loongarch-randconfig-r001-20230818
> | `-- arch-loongarch-include-asm-atomic.h:warning:array-subscript-is-outside-array-bounds-of-struct-cpumask
> |-- mips-randconfig-r012-20230818
> | `-- include-asm-generic-unaligned.h:warning:array-subscript-is-outside-array-bounds-of-unsigned-char
> |-- sparc-randconfig-r026-20230818
> | `-- arch-sparc-include-asm-string.h:warning:__builtin_memcpy-forming-offset-is-out-of-the-bounds-of-object-send_data-with-type-u8-aka-unsigned-char
> `-- x86_64-defconfig
> |-- lib-vsprintf.c:warning:writing-byte-into-a-region-of-size
> `-- mm-mempolicy.c:warning:writing-byte-into-a-region-of-size
>
> elapsed time: 845m
>
> configs tested: 111
> configs skipped: 4
>
Powered by blists - more mailing lists