public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: kernel test robot <lkp@intel.com>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	"Liu, Yujie" <yujie.liu@intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [gustavoars:testing/fam01-next20230817] BUILD SUCCESS WITH WARNING dbd3e479335bc8b09ea540102109ac38b0a73336
Date: Sun, 27 Aug 2023 10:18:57 +0800	[thread overview]
Message-ID: <ZOqykd6tVGip+Swy@rli9-mobl> (raw)
In-Reply-To: <d8fd6210-84eb-6d32-6486-1d90c86186ca@embeddedor.com>

On Mon, Aug 21, 2023 at 11:26:17AM -0600, Gustavo A. R. Silva wrote:
> 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`

Thanks Gustavo for the input, we will add detail version of compiler in the
summary report.

We will start with the line you suggested, and later will look for a way
to add it to the warning line since multiple gcc/clang could be involved
in one round test.

Thanks

> 
> 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
> > 

  reply	other threads:[~2023-08-27  2:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  7:55 [gustavoars:testing/fam01-next20230817] BUILD SUCCESS WITH WARNING dbd3e479335bc8b09ea540102109ac38b0a73336 kernel test robot
2023-08-21 17:26 ` Gustavo A. R. Silva
2023-08-27  2:18   ` Philip Li [this message]
2023-09-10 19:43     ` Gustavo A. R. Silva

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=ZOqykd6tVGip+Swy@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=gustavo@embeddedor.com \
    --cc=gustavoars@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=yujie.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox