From: Nathan Chancellor <nathan@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
clang-built-linux <llvm@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
linux-hardening@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
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-20250804: clang-nightly hardening.config boot failed on arm64 rock-pi-4b
Date: Mon, 4 Aug 2025 10:53:38 -0700 [thread overview]
Message-ID: <20250804175338.GA2197404@ax162> (raw)
In-Reply-To: <202508040843.CCEFEF9ED@keescook>
On Mon, Aug 04, 2025 at 08:44:16AM -0700, Kees Cook wrote:
> On Mon, Aug 04, 2025 at 03:41:51PM +0530, Naresh Kamboju wrote:
> > Regressions found while booting the Linux next-20250804 on the
> > qemu-arm64, dragonboard-410c, rock-pi-4b due to following kernel log.
> >
> > Regression Analysis:
> > - New regression? Yes
> > - Reproducibility? yes
> >
> > First seen on the next-20250804
> > Good: next-20250801
> > Bad: next-20250804
>
> Are you able to bisect this by any chance?
I think this is the runtime manifestation of
https://github.com/ClangBuiltLinux/linux/issues/2116 when built with a
version of LLVM without assertions (when assertions are enabled, the
build just fails). I can reproduce this with a version of LLVM that
contains the broken change and it is resolved with a version of LLVM
that contains Fangrui's fixes. I assume this should hit LKFT in the next
couple of days via apt.llvm.org.
Cheers,
Nathan
prev parent reply other threads:[~2025-08-04 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 10:11 next-20250804: clang-nightly hardening.config boot failed on arm64 rock-pi-4b Naresh Kamboju
2025-08-04 15:44 ` Kees Cook
2025-08-04 17:53 ` Nathan Chancellor [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=20250804175338.GA2197404@ax162 \
--to=nathan@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.