From: "Arnd Bergmann" <arnd@arndb.de>
To: "Dan Carpenter" <dan.carpenter@linaro.org>
Cc: stable@vger.kernel.org,
"laurent.pinchart" <laurent.pinchart@ideasonboard.com>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
"Randy Dunlap" <rdunlap@infradead.org>
Subject: Re: randconfig fixes for 5.10.y
Date: Tue, 30 May 2023 21:02:38 +0200 [thread overview]
Message-ID: <2fce7746-6d63-4853-9b20-8fa0b24d6f32@app.fastmail.com> (raw)
In-Reply-To: <6b1a0ee6-c78b-4873-bfd5-89798fce9899@kili.mountain>
On Tue, May 30, 2023, at 17:38, Dan Carpenter wrote:
> On Tue, May 30, 2023 at 10:53:55AM +0200, Arnd Bergmann wrote:
>> On Tue, May 30, 2023, at 10:22, Dan Carpenter wrote:
>
> Ah, yeah. Thanks. Scripting to automatically bisect would be useful.
> Btw, I reported one that isn't fixed on randconfig-6.4.
>
> https://lore.kernel.org/all/1770d098-8dc7-4906-bed2-1addf8a6794d@kili.mountain/
>
> CC [M] crypto/twofish_common.o
> crypto/twofish_common.c: In function ‘__twofish_setkey’:
> crypto/twofish_common.c:683:1: warning: the frame size of 2064 bytes is
> larger than 2048 bytes [-Wframe-larger-than=]
> 683 | }
> | ^
> CHECK crypto/twofish_common.c
Thanks for the report, I forgot about this bit.
I have a small fragment that I pass to the randconfig generator
to avoid some common problems and also give me much faster
builds:
# maximize search space, disable options not worth testing
CONFIG_COMPILE_TEST=y
# reduce compile-time dependencies
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_COMPILE_TEST=y forces a number of options to be
hidden from build tests, which is generally super useful.
The one that ended up hiding the stack growth above is
CONFIG_GCOV_PROFILE_ALL. I'll try enabling it for a few
builds to see what else shows up with it.
Arnd
next prev parent reply other threads:[~2023-05-30 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 8:22 randconfig fixes for 5.10.y Dan Carpenter
2023-05-30 8:53 ` Arnd Bergmann
2023-05-30 15:38 ` Dan Carpenter
2023-05-30 19:02 ` Arnd Bergmann [this message]
2023-05-30 19:20 ` Arnd Bergmann
2023-05-31 10:12 ` Arnd Bergmann
2023-05-31 16:37 ` Nick Desaulniers
2023-06-07 17:55 ` Greg KH
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=2fce7746-6d63-4853-9b20-8fa0b24d6f32@app.fastmail.com \
--to=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.org \
--cc=stable@vger.kernel.org \
/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