linux-kernel - Re: [PATCH v3 0/4] sparc64: Jump to boot prom from console on panic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20170201.145031.295104986575080480.davem@davemloft.net>
Date:   Wed, 01 Feb 2017 14:50:31 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     vijay.ac.kumar@...cle.com
Cc:     sparclinux@...r.kernel.org, karl.volz@...cle.com,
        rob.gardner@...cle.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/4] sparc64: Jump to boot prom from console on panic

From: Vijay Kumar <vijay.ac.kumar@...cle.com>
Date: Wed,  1 Feb 2017 11:34:36 -0800

> Currently Stop-A (L1A) does not make the kernel switch to OBP on panic.

This is intentional, the kernel prints a message telling the user to
press break (L1-A) if they want to drop out of the kernel and we force
the break to be allowed by setting stop_a_enabled.

I'm wondering why there is so much effort being directed into BRK
behavior.

If you want to break into the OK prompt, have the reboot-cmd
environment variable set appropriately, and simply hit BRK and it will
work in both ldom and non-ldom environments.