From: Arnd Bergmann <arnd@arndb.de>
To: Philip Li <philip.li@intel.com>
Cc: Rong Chen <rong.a.chen@intel.com>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
clang-built-linux <clang-built-linux@googlegroups.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nathan Chancellor <nathan@kernel.org>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [kbuild-all] Re: [linux-stable-rc:linux-5.10.y 3189/5262] drivers/usb/dwc2/hcd.c:3835:6: warning: stack frame size of 1032 bytes in function 'dwc2_hcd_dump_state'
Date: Fri, 21 May 2021 10:09:54 +0200 [thread overview]
Message-ID: <CAK8P3a3e4zygAJ6cwWAtZey_G_NL8-+BFwB21GxMA-zT_rtGgw@mail.gmail.com> (raw)
In-Reply-To: <20210521005724.GA3353474@pl-dbox>
On Fri, May 21, 2021 at 3:00 AM Philip Li <philip.li@intel.com> wrote:
> On Thu, May 20, 2021 at 05:56:35PM +0800, Rong Chen wrote:
> > On 5/20/21 5:27 PM, Arnd Bergmann wrote:
> > > On Thu, May 20, 2021 at 11:22 AM Rong Chen <rong.a.chen@intel.com> wrote:
> > > >
> > > > We have disabled CONFIG_UBSAN_ALIGNMENT for mips/clang in our kconfigs
> > > > to avoid reporting such warnings again.
> > > Thanks a lot, that helps.
> > >
> > > Have you considered always enforcing CONFIG_COMPILE_TEST=y for any
> > > randconfig build? That would address this issue along with a number of similar
>
> Hi Arnd, thanks for feedback, we have talked about this internally. We use randconfig
> to cover different combination, some randconfig would have CONFIG_COMPILE_TEST=y, some
> is not. For now, we also want to check the kernel build status when COMPILE_TEST is
> not set (as if this is a valid kconfig combination). Thus we may not always enforcing
> the y here, but keep it as random as possible.
Ok, I see.
(Adding Masahiro Yamada)
I think there was a patch in the past would let Kconfig detect whether
a kernel is built using
'make randconfig', and add further dependencies based on this, to
detect combinations
that we want to avoid testing in such environments. Maybe we should
revisit that and
replace the 'depends on !COMPILE_TEST' checks.
Arnd
prev parent reply other threads:[~2021-05-21 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 19:48 kernel test robot
2021-05-19 20:28 ` Arnd Bergmann
2021-05-20 9:20 ` Rong Chen
2021-05-20 9:27 ` Arnd Bergmann
2021-05-20 9:56 ` [kbuild-all] " Rong Chen
2021-05-21 0:57 ` Philip Li
2021-05-21 8:09 ` Arnd Bergmann [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=CAK8P3a3e4zygAJ6cwWAtZey_G_NL8-+BFwB21GxMA-zT_rtGgw@mail.gmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=philip.li@intel.com \
--cc=rong.a.chen@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