From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Masahiro Yamada <masahiroy@kernel.org>, Will Deacon <will@kernel.org>
Cc: linux-arch@vger.kernel.org, Nicolas Schier <nicolas@fjasle.eu>,
linux-kernel@vger.kernel.org, Dennis Gilmore <dennis@ausil.us>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
Ard Biesheuvel <ardb@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: BUG: arm64: missing build-id from vmlinux
Date: Wed, 21 Dec 2022 09:23:24 +0100 [thread overview]
Message-ID: <26bd2928-9d62-32b3-4f9f-9dd9293cefeb@leemhuis.info> (raw)
In-Reply-To: <CAABkxwuQoz1CTbyb57n0ZX65eSYiTonFCU8-LCQc=74D=xE=rA@mail.gmail.com>
Hi, this is your Linux kernel regression tracker. CCing the regression
mailing list, as it should be in the loop for all regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html
On 18.12.22 21:51, Dennis Gilmore wrote:
> The changes in https://lore.kernel.org/linux-arm-kernel/166783716442.32724.935158280857906499.b4-ty@kernel.org/T/
> result in vmlinux no longer having a build-id.
FWIW, that's 994b7ac1697b ("arm64: remove special treatment for the link
order of head.o") from Masahiro merged through Will this cycle.
> At the least, this
> causes rpm builds to fail. Reverting the patch does bring back a
> build-id, but there may be a different way to fix the regression
Makes me wonder if other distros or CIs relying on the build-id are
broken, too.
Anyway, the holiday season is upon us, hence I also wonder if it would
be best to revert above change quickly and leave further debugging for 2023.
Masahiro, Will, what's your option on this?
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
#regzbot ^introduced 994b7ac1697b
#regzbot title arm64: missing build-id in vmlinux breaks at leas
Fedora's kernel packaging
#regzbot ignore-activity
next prev parent reply other threads:[~2022-12-21 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 20:51 BUG: arm64: missing build-id from vmlinux Dennis Gilmore
2022-12-21 8:23 ` Thorsten Leemhuis [this message]
2022-12-21 15:39 ` Masahiro Yamada
2022-12-21 16:29 ` Thorsten Leemhuis
2022-12-22 11:53 ` Ard Biesheuvel
2022-12-25 2:16 ` Masahiro Yamada
2022-12-25 9:01 ` Ard Biesheuvel
2023-01-11 17:04 ` Justin Forbes
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=26bd2928-9d62-32b3-4f9f-9dd9293cefeb@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dennis@ausil.us \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=regressions@lists.linux.dev \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).