From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [BUILD BUG] regression from certs: Move load_certificate_list() to be with the asymmetric keys code #forregzbot
Date: Wed, 13 Jul 2022 08:07:10 +0200 [thread overview]
Message-ID: <85f80df3-0343-b231-755d-7c1eb7a2c0c5@leemhuis.info> (raw)
In-Reply-To: <20220712104554.408dbf42@gandalf.local.home>
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
On 12.07.22 16:45, Steven Rostedt wrote:
>
> I have a config that now fails to build due to commit 60050ffe3d770
> ("certs: Move load_certificate_list() to be with the asymmetric keys code")
>
> CC .vmlinux.export.o
> LD .tmp_vmlinux.kallsyms1
> ld: certs/system_keyring.o: in function `load_system_certificate_list':
> system_keyring.c:(.init.text+0x35): undefined reference to `x509_load_certificate_list'
> make[1]: *** [/work/build/trace/nobackup/linux-test.git/Makefile:1164: vmlinux] Error 1
> make[1]: Leaving directory '/work/build/trace/nobackup/mxtest'
> make: *** [Makefile:219: __sub-make] Error 2
>
>
> If I revert this commit, it builds fine.
>
Thanks for the report. To be sure below issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
tracking bot:
#regzbot ^introduced 60050ffe3d770
#regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/
Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replies to), as explained for
in the Linux kernel's documentation; above webpage explains why this is
important for tracked regressions.
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.
parent reply other threads:[~2022-07-13 6:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220712104554.408dbf42@gandalf.local.home>]
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=85f80df3-0343-b231-755d-7c1eb7a2c0c5@leemhuis.info \
--to=regressions@leemhuis.info \
--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;
as well as URLs for NNTP newsgroup(s).