[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180306042957.GE6713@jagdpanzerIV>
Date: Tue, 6 Mar 2018 13:29:57 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Tejun Heo <tj@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Dave Young <dyoung@...hat.com>,
Andi Kleen <ak@...ux.intel.com>,
Greentime Hu <green.hu@...il.com>,
Vincent Chen <deanbo422@...il.com>,
Arnd Bergmann <arnd@...db.de>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
adi-buildroot-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: Re: [PATCH] dump_stack: convert generic dump_stack into a weak symbol
On (03/05/18 15:48), Petr Mladek wrote:
[..]
>
> I hope that I did not miss anything. I could not try this at
> runtime.
I think you can. The rules are universal, you can do on x86
something like this
---
arch/x86/kernel/dumpstack.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/arch/x86/kernel/dumpstack.c b/arch/x86/kernel/dumpstack.c
index a2d8a3908670..5d45f406717e 100644
--- a/arch/x86/kernel/dumpstack.c
+++ b/arch/x86/kernel/dumpstack.c
@@ -375,3 +375,16 @@ static int __init code_bytes_setup(char *s)
return 1;
}
__setup("code_bytes=", code_bytes_setup);
+
+void dump_stack(void)
+{
+ dump_stack_print_info(KERN_DEFAULT);
+
+ pr_crit("\t\tLinux\n\n");
+
+ pr_crit("An error has occurred. To continue:\n"
+ "Press Enter to return to Linux, or\n"
+ "Press CTRL+ALT+DEL to restart your computer.\n");
+
+ pr_crit("\n\n\tPress any key to continue _");
+}
---
Should be enough for testing.
> Anyway, from my side:
>
> Reviewed-by: Petr Mladek <pmladek@...e.com>
Thanks.
-ss
Powered by blists - more mailing lists