From: "Liu, Yujie" <yujie.liu@intel.com>
To: "ansuelsmth@gmail.com" <ansuelsmth@gmail.com>
Cc: "Li, Philip" <philip.li@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
lkp <lkp@intel.com>, "andrew@lunn.ch" <andrew@lunn.ch>
Subject: Re: drivers/leds/trigger/ledtrig-netdev.c:120:34: warning: array subscript 17 is above array bounds of 'char[16]'
Date: Sun, 8 Oct 2023 00:36:18 +0000 [thread overview]
Message-ID: <60787698c39afac5441976ddd32ecf7a5645e680.camel@intel.com> (raw)
In-Reply-To: <652159fd.050a0220.141f8.cba3@mx.google.com>
On Sat, 2023-10-07 at 15:15 +0200, Christian Marangi wrote:
> > > > >
> > > > > Can't repro so I guess this was a false-positive that got
> > > > > fixed?
> > > > > (I used
> > > > > the repro commands and doesn't print any error)
> > > >
> > > > Hi Ansuel, the issue requires to build with -Warray-bounds
> > > > flag. We
> > > > will fix
> > > > the reproduce steps in earliest time. Sorry for the
> > > > inconvenience.
> > > >
> > >
> > > Hi again, happy to help you further.
> > >
> > > By adding the flag I still can't repro.
> > > I'm using this command.
> > > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-13.2.0
> > > ~/bin/make.cross
> > > W=1 O=build_dir ARCH=loongarch SHELL=/bin/bash
> > > drivers/leds/trigger/
> > > -Warray-bounds
> >
> > Hi Ansuel, we added some extra compiler flags recently but the
> > repro
> > steps were not updated in time. Sorry for this.
> >
> > Could you please have a try with the following command? (append
> > KCFLAGS="-Warray-bounds" at the end)
> >
> > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-13.2.0
> > ~/bin/make.cross W=1 O=build_dir ARCH=loongarch SHELL=/bin/bash
> > drivers/leds/trigger/ KCFLAGS="-Warray-bounds"
> >
>
> Can confirm this worked! (also sent patch upstream)
>
> May I suggest some improvement to the repro script?
>
> I would add some instruction on the cleanup... A simple rm -rf with all
> the toolchain and directory downloaded may be useful.
>
> Also some reference on the config to download to exactly repro the
> error? If someone doesn't download the config from the mail, the default
> kernel config for the ARCH is used and the bug is not repro.
>
> I know these are all steps that a kernel dev should already know but
> since we are giving instructions, it might not be a bad idea to include
> every required step.
Thanks a lot for the suggestion. We will soon be refining the repro
instructions to be more accurate.
Best Regards,
Yujie
prev parent reply other threads:[~2023-10-08 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 12:21 kernel test robot
2023-09-25 23:22 ` Christian Marangi
2023-09-27 14:44 ` Philip Li
2023-09-29 10:26 ` Christian Marangi
2023-10-07 7:17 ` Liu, Yujie
2023-10-07 13:15 ` Christian Marangi
2023-10-08 0:36 ` Liu, Yujie [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=60787698c39afac5441976ddd32ecf7a5645e680.camel@intel.com \
--to=yujie.liu@intel.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=philip.li@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
all inboxes | Powered by JetHome®