[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202507251739.E62B1C95@keescook>
Date: Fri, 25 Jul 2025 17:40:09 -0700
From: Kees Cook <kees@...nel.org>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
Linux Regressions <regressions@...ts.linux.dev>,
Arnd Bergmann <arnd@...db.de>,
Dan Carpenter <dan.carpenter@...aro.org>,
Anders Roxell <anders.roxell@...aro.org>,
Ben Copeland <benjamin.copeland@...aro.org>
Subject: Re: next-20250723 arm atags_to_fdt.c undefined reference to
`__sanitizer_cov_stack_depth'
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
Powered by blists - more mailing lists