From: David Howells <dhowells@redhat.com>
To: =?UTF-8?q?Micka=C3=ABl=20Sala=C3=BCn?= <mic@digikod.net>
Cc: dhowells@redhat.com, "Jarkko Sakkinen" <jarkko@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
"David Woodhouse" <dwmw2@infradead.org>,
"Eric Snowberg" <eric.snowberg@oracle.com>,
"Paul Moore" <paul@paul-moore.com>,
"Tyler Hicks" <tyhicks@linux.microsoft.com>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org,
=?UTF-8?q?Micka=C3=ABl=20Sala=C3=BCn?= <mic@linux.microsoft.com>
Subject: Re: [PATCH v2 1/1] certs: Explain the rationale to call panic()
Date: Wed, 30 Mar 2022 13:53:26 +0100 [thread overview]
Message-ID: <2933967.1648644806@warthog.procyon.org.uk> (raw)
In-Reply-To: <20220322111323.542184-2-mic@digikod.net>
Mickaël Salaün <mic@digikod.net> wrote:
> The blacklist_init() function calls panic() for memory allocation
> errors. This change documents the reason why we don't return -ENODEV.
Why, though?
This is only called whilst the kernel is booting. If you hit ENOMEM, you
aren't likely to get much further with the boot process.
David
prev parent reply other threads:[~2022-03-30 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 11:13 [PATCH v2 0/1] Explain panic() calls for keyring initialization Mickaël Salaün
2022-03-22 11:13 ` [PATCH v2 1/1] certs: Explain the rationale to call panic() Mickaël Salaün
2022-03-22 17:39 ` Tyler Hicks
2022-03-22 20:31 ` Jarkko Sakkinen
2022-03-30 12:53 ` David Howells [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=2933967.1648644806@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=eric.snowberg@oracle.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=mic@linux.microsoft.com \
--cc=paul@paul-moore.com \
--cc=tyhicks@linux.microsoft.com \
/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).