From: Kees Cook <kees@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Ben Copeland <benjamin.copeland@linaro.org>
Subject: Re: next-20250723 arm atags_to_fdt.c undefined reference to `__sanitizer_cov_stack_depth'
Date: Fri, 25 Jul 2025 17:40:09 -0700 [thread overview]
Message-ID: <202507251739.E62B1C95@keescook> (raw)
In-Reply-To: <aINJTDD3je4XJ6VO@shell.armlinux.org.uk>
On Fri, Jul 25, 2025 at 10:07:24AM +0100, Russell King (Oracle) wrote:
> On Fri, Jul 25, 2025 at 01:59:02PM +0530, Naresh Kamboju wrote:
> > Regressions noticed while building arm builds with gcc-13 and gcc-8
> > toolchains on the Linux next-20250723 to next-20250725 tags.
> >
> > First seen on the Linux next-20250723
> > Good: next-20250722
> > Bad: next-20250723 and next-20250725
> >
> > Regression Analysis:
> > - New regression? Yes
> > - Reproducibility? Yes
> >
> > ## Build regressions
> > * arm, build
> > - gcc-13-lkftconfig-hardening
> > - gcc-8-lkftconfig-hardening
> >
> > Build regression: next-20250723 arm atags_to_fdt.c undefined reference
> > to `__sanitizer_cov_stack_depth'
>
> "cov" suggests "coverty", and that the symbol is not available in the
> kernel suggests that coverty isn't supported.
This is the coverage sanitizer and related to my changes. Sorry! This
didn't show up in my build testing, I'll reproduce it and get it fixed.
--
Kees Cook
prev parent reply other threads:[~2025-07-26 0:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 8:29 next-20250723 arm atags_to_fdt.c undefined reference to `__sanitizer_cov_stack_depth' Naresh Kamboju
2025-07-25 9:07 ` Russell King (Oracle)
2025-07-26 0:40 ` Kees Cook [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=202507251739.E62B1C95@keescook \
--to=kees@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
/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