From: Ingo Molnar <mingo@elte.hu>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@osdl.org, mingo@redhat.com, linux-kernel@vger.kernel.org,
ak@suse.de, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] x86_64: remove empty lines from stack traces/oopses
Date: Mon, 11 Aug 2008 19:02:19 +0200 [thread overview]
Message-ID: <20080811170219.GJ4524@elte.hu> (raw)
In-Reply-To: <20080731235137.GA4816@martell.zuzino.mipt.ru>
* Alexey Dobriyan <adobriyan@gmail.com> wrote:
> show_trace_log_lvl(struct task_struct *task, struct pt_regs *regs,
> unsigned long *stack, unsigned long bp, char *log_lvl)
> {
> - printk("\nCall Trace:\n");
> + printk("Call Trace:\n");
> dump_trace(task, regs, stack, bp, &print_trace_ops, log_lvl);
> - printk("\n");
> }
hm, it's nice to have stack traces stand out a bit, and to not get the
'Call Trace' embedded in the middle of a printk (which happens to crash
or produce a stack dump).
> void show_trace(struct task_struct *task, struct pt_regs *regs,
> @@ -386,6 +385,7 @@ show_stack_log_lvl(struct task_struct *task, struct pt_regs *regs,
> printk(" %016lx", *stack++);
> touch_nmi_watchdog();
> }
> + printk("\n");
> show_trace_log_lvl(task, regs, sp, bp, log_lvl);
> }
>
> @@ -443,7 +443,6 @@ void show_registers(struct pt_regs *regs)
> printk("Stack: ");
> show_stack_log_lvl(NULL, regs, (unsigned long *)sp,
> regs->bp, "");
> - printk("\n");
>
> printk(KERN_EMERG "Code: ");
just to make sure i get the gist of your change, do you have a 'before'
and 'after' sample oops, so that we can see the difference?
Ingo
next prev parent reply other threads:[~2008-08-11 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 23:51 Alexey Dobriyan
2008-08-11 17:02 ` Ingo Molnar [this message]
2008-08-11 19:22 ` Alexey Dobriyan
2008-08-15 15:25 ` Ingo Molnar
2008-08-15 15:49 ` Arjan van de Ven
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=20080811170219.GJ4524@elte.hu \
--to=mingo@elte.hu \
--cc=adobriyan@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®