From: Eric Snowberg <eric.snowberg@oracle.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
David Howells <dhowells@redhat.com>,
nathan@kernel.org, dwmw2@infradead.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] certs: Fix wrong kconfig option used for x509_revocation_list
Date: Wed, 10 Mar 2021 17:04:02 -0700 [thread overview]
Message-ID: <49B7E289-5B29-4173-8C3A-A0D1BA95AC10@oracle.com> (raw)
In-Reply-To: <YEkhYtQD68Qy/gcA@kernel.org>
> On Mar 10, 2021, at 12:43 PM, Jarkko Sakkinen <jarkko@kernel.org> wrote:
>
> On Thu, Mar 04, 2021 at 12:50:30PM -0500, Eric Snowberg wrote:
>> Fix a build issue when x509_revocation_list is not defined.
>>
>> $ make ARCH=x86_64 O=build64 all
>>
>> EXTRACT_CERTS ../
>> At main.c:154:
>> - SSL error:0909006C:PEM routines:get_name:no start line: crypto/pem/pem_lib.c:745
>> extract-cert: ../: Is a directory
>> make[2]: [../certs/Makefile:119: certs/x509_revocation_list] Error 1 (ignored)
>>
>> When the new CONFIG_SYSTEM_REVOCATION_LIST was added [1], it was not carried
>> into the code for preloading the revocation certificates [2]. Change from
>> using the original CONFIG_SYSTEM_BLACKLIST_KEYRING to the new
>> CONFIG_SYSTEM_REVOCATION_LIST.
>>
>> [1] https://lore.kernel.org/keyrings/EDA280F9-F72D-4181-93C7-CDBE95976FF7@oracle.com/T/#m562c1b27bf402190e7bb573ad20eff5b6310d08f
>> [2] https://lore.kernel.org/keyrings/EDA280F9-F72D-4181-93C7-CDBE95976FF7@oracle.com/T/#m07e258bf019ccbac23820fad5192ceffa74fc6ab
>>
>> Reported-by: Randy Dunlap <rdunlap@infradead.org>
>> Signed-off-by: Eric Snowberg <eric.snowberg@oracle.com>
>
> Got my first ever chance to try out b4:
>
> $ b4 am 20210304175030.184131-1-eric.snowberg@oracle.com
> Looking up https://lore.kernel.org/r/20210304175030.184131-1-eric.snowberg%40oracle.com
> Grabbing thread from lore.kernel.org/keyrings
> Analyzing 5 messages in the thread
> ---
> Writing ./v2_20210304_eric_snowberg_certs_fix_wrong_kconfig_option_used_for_x509_revocation_list.mbx
> ✓ [PATCH v2] certs: Fix wrong kconfig option used for x509_revocation_list
> + Tested-by: Nathan Chancellor <nathan@kernel.org> (✓ DKIM/kernel.org)
> ---
> ✓ Attestation-by: DKIM/oracle.com (From: eric.snowberg@oracle.com)
> ---
> Total patches: 1
> ---
> Link: https://lore.kernel.org/r/20210304175030.184131-1-eric.snowberg@oracle.com
> Base: not found
> git am ./v2_20210304_eric_snowberg_certs_fix_wrong_kconfig_option_used_for_x509_revocation_list.mbx
>
> Wondering tho, what "Base: not found" means?
This was based off David’s keys-next branch, which I think has now
changed. I probably should have sent this with the following base-commit:
base-commit: ea20ea8b8ba4d475ebc79da63350850780933a81
I’ll try to remember to make sure to have the base-commit added in
the future.
prev parent reply other threads:[~2021-03-11 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 17:50 [PATCH v2] certs: Fix wrong kconfig option used for x509_revocation_list Eric Snowberg
2021-03-04 18:10 ` Nathan Chancellor
2021-03-05 21:50 ` David Howells
2021-03-09 2:28 ` Eric Snowberg
2021-03-09 11:46 ` David Howells
2021-03-10 19:43 ` Jarkko Sakkinen
2021-03-10 19:44 ` Jarkko Sakkinen
2021-03-11 0:04 ` Eric Snowberg [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=49B7E289-5B29-4173-8C3A-A0D1BA95AC10@oracle.com \
--to=eric.snowberg@oracle.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=rdunlap@infradead.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).