From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Tejun Heo <tj@kernel.org>, Steven Rostedt <rostedt@goodmis.org>,
Dave Young <dyoung@redhat.com>, Andi Kleen <ak@linux.intel.com>,
Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
adi-buildroot-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] dump_stack: convert generic dump_stack into a weak symbol
Date: Tue, 6 Mar 2018 13:29:57 +0900 [thread overview]
Message-ID: <20180306042957.GE6713@jagdpanzerIV> (raw)
In-Reply-To: <20180305144846.3jommv372c73dltt@pathway.suse.cz>
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@suse.com>
Thanks.
-ss
next prev parent reply other threads:[~2018-03-06 4:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 5:37 [PATCH] dump_stack: convert generic dump_stack into a weak symbol Sergey Senozhatsky
2018-03-05 14:48 ` Petr Mladek
2018-03-06 2:50 ` Greentime Hu
2018-03-06 4:31 ` Sergey Senozhatsky
2018-03-06 5:34 ` Greentime Hu
2018-03-06 4:29 ` Sergey Senozhatsky [this message]
2018-03-06 12:43 ` Petr Mladek
2018-03-06 22:52 ` Stephen Rothwell
2018-03-06 13:27 ` Arnd Bergmann
2018-03-07 2:21 ` Sergey Senozhatsky
2018-03-07 8:46 ` Arnd Bergmann
2018-03-07 9:09 ` Petr Mladek
2018-03-07 9:44 ` Greentime Hu
2018-03-07 9:50 ` Arnd Bergmann
2018-03-07 10:40 ` Sergey Senozhatsky
2018-03-07 10:57 ` Arnd Bergmann
2018-03-07 11:48 ` Sergey Senozhatsky
2018-03-07 12:41 ` Stephen Rothwell
2018-03-07 12:48 ` Arnd Bergmann
2018-03-07 12:53 ` Stephen Rothwell
2018-03-07 12:58 ` Arnd Bergmann
2018-03-07 13:10 ` Stephen Rothwell
2018-03-07 13:40 ` Sergey Senozhatsky
2018-03-07 14:01 ` Sergey Senozhatsky
2018-03-09 9:50 ` Petr Mladek
2018-03-14 23:42 ` Steven Rostedt
2018-03-14 23:58 ` Stephen Rothwell
2018-03-07 8:49 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180306042957.GE6713@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=deanbo422@gmail.com \
--cc=dyoung@redhat.com \
--cc=green.hu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).