[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2090DOT3q5CX9kV@hirez.programming.kicks-ass.net>
Date: Thu, 10 Nov 2022 19:07:12 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Ross Philipson <ross.philipson@...cle.com>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
dpsmith@...rtussolutions.com, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, hpa@...or.com, luto@...capital.net,
dave.hansen@...ux.intel.com, kanth.ghatraju@...cle.com,
trenchboot-devel@...glegroups.com, jailhouse-dev@...glegroups.com,
jan.kiszka@...mens.com, xen-devel@...ts.xenproject.org,
jgross@...e.com, boris.ostrovsky@...cle.com,
andrew.cooper3@...rix.com
Subject: Re: [PATCH v2 2/2] x86: Check return values from early_ioremap calls
On Thu, Nov 10, 2022 at 03:45:21PM +0000, Ross Philipson wrote:
> On allocation failures, panic() was used since this seemed
> to be the action taken on other failures in the modules
> touched by this patch.
How is the panic() more useful than the obvious NULL deref that also
splats?
Powered by blists - more mailing lists