[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2933967.1648644806@warthog.procyon.org.uk>
Date: Wed, 30 Mar 2022 13:53:26 +0100
From: David Howells <dhowells@...hat.com>
To: =?UTF-8?q?Micka=C3=ABl=20Sala=C3=BCn?= <mic@...ikod.net>
Cc: dhowells@...hat.com, Jarkko Sakkinen <jarkko@...nel.org>,
"David S . Miller" <davem@...emloft.net>,
David Woodhouse <dwmw2@...radead.org>,
Eric Snowberg <eric.snowberg@...cle.com>,
Paul Moore <paul@...l-moore.com>,
Tyler Hicks <tyhicks@...ux.microsoft.com>,
keyrings@...r.kernel.org, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org,
=?UTF-8?q?Micka=C3=ABl=20Sala=C3=BCn?=
<mic@...ux.microsoft.com>
Subject: Re: [PATCH v2 1/1] certs: Explain the rationale to call panic()
Mickaël Salaün <mic@...ikod.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
Powered by blists - more mailing lists