summaryrefslogtreecommitdiff
path: root/drivers/scsi
diff options
context:
space:
mode:
authorJames Morse <james.morse@arm.com>2019-01-29 18:48:37 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-12-05 15:38:02 +0100
commit3ad61d642b69e42554a14eba7f18cbb20f1d6f61 (patch)
tree4dd27e4737188165819c6ef8711db6f12bce1d65 /drivers/scsi
parent6e2dd42cede242f4ca4e7205f51c8b9ff706ca5c (diff)
ACPI / APEI: Don't wait to serialise with oops messages when panic()ing
[ Upstream commit 78b0b690f6558ed788dccafa45965325dd11ba89 ] oops_begin() exists to group printk() messages with the oops message printed by die(). To reach this caller we know that platform firmware took this error first, then notified the OS via NMI with a 'panic' severity. Don't wait for another CPU to release the die-lock before panic()ing, our only goal is to print this fatal error and panic(). This code is always called in_nmi(), and since commit 42a0bb3f7138 ("printk/nmi: generic solution for safe printk in NMI"), it has been safe to call printk() from this context. Messages are batched in a per-cpu buffer and printed via irq-work, or a call back from panic(). Link: https://patchwork.kernel.org/patch/10313555/ Acked-by: Borislav Petkov <bp@suse.de> Signed-off-by: James Morse <james.morse@arm.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/scsi')
0 files changed, 0 insertions, 0 deletions