mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Toralf Förster" <toralf.foerster@gmx.de>,
	"Alexander Tsoy" <alexander@tsoy.me>,
	stable <stable@vger.kernel.org>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>,
	"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: 4.14.9 doesn't boot (regression)
Date: Fri, 29 Dec 2017 21:49:47 -0600	[thread overview]
Message-ID: <20171230034947.6jgk5t7c7jrl6dwg@treble> (raw)
In-Reply-To: <7A0A9B37-20FF-4B17-B4F5-D8B999269FC4@amacapital.net>

On Fri, Dec 29, 2017 at 05:10:35PM -0700, Andy Lutomirski wrote:
> (Also, Josh, the oops code should have printed the contents of the
> struct pt_regs at the top of the DF stack.  Any idea why it didn't?)

Looking at one of the dumps:

  [  392.774879] NMI backtrace for cpu 0
  [  392.774881] CPU: 0 PID: 1 Comm: init Not tainted 4.14.9-gentoo #1
  [  392.774881] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
  [  392.774882] task: ffff8802368b8000 task.stack: ffffc9000000c000
  [  392.774885] RIP: 0010:double_fault+0x0/0x30
  [  392.774886] RSP: 0000:ffffffffff527fd0 EFLAGS: 00000086
  [  392.774887] RAX: 000000003fc00000 RBX: 0000000000000001 RCX: 00000000c0000101
  [  392.774887] RDX: 00000000ffff8802 RSI: 0000000000000000 RDI: ffffffffff527f58
  [  392.774887] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
  [  392.774888] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff816ae726
  [  392.774888] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
  [  392.774889] FS:  0000000000000000(0000) GS:ffff88023fc00000(0000) knlGS:0000000000000000
  [  392.774889] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
  [  392.774890] CR2: ffffffffff526f08 CR3: 0000000235b48002 CR4: 00000000001606f0
  [  392.774892] Call Trace:
  [  392.774894]  <#DF>
  [  392.774897]  do_double_fault+0xb/0x140
  [  392.774898]  </#DF>

It should have at least printed the #DF iret frame registers, which I
recently added support for in "x86/unwinder: Handle stack overflows more
gracefully", which is in both 4.14.9 and 4.15-rc5.

I think the missing iret regs are due to a bug in show_trace_log_lvl(),
where if the unwind starts with two regs frames in a row, the second
regs don't get printed.

Alexander, would you mind reproducing again with the below patch?  It
should still fail, but this time it should hopefully show another
RIP/RSP/EFLAGS instead of the "do_double_fault+0xb/0x140" line.


diff --git a/arch/x86/kernel/dumpstack.c b/arch/x86/kernel/dumpstack.c
index 36b17e0febe8..39a320d077aa 100644
--- a/arch/x86/kernel/dumpstack.c
+++ b/arch/x86/kernel/dumpstack.c
@@ -103,6 +103,7 @@ void show_trace_log_lvl(struct task_struct *task, struct pt_regs *regs,
 
 	unwind_start(&state, task, regs, stack);
 	stack = stack ? : get_stack_pointer(task, regs);
+	regs = unwind_get_entry_regs(&state);
 
 	/*
 	 * Iterate through the stacks, starting with the current stack pointer.
@@ -120,7 +121,7 @@ void show_trace_log_lvl(struct task_struct *task, struct pt_regs *regs,
 	 * - hardirq stack
 	 * - entry stack
 	 */
-	for (regs = NULL; stack; stack = PTR_ALIGN(stack_info.next_sp, sizeof(long))) {
+	for ( ; stack; stack = PTR_ALIGN(stack_info.next_sp, sizeof(long))) {
 		const char *stack_name;
 
 		if (get_stack_info(stack, task, &stack_info, &visit_mask)) {

  parent reply	other threads:[~2017-12-30  3:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 11:14 Toralf Förster
2017-12-29 13:33 ` Sebastian Gottschall
2017-12-29 13:38   ` Toralf Förster
2017-12-29 15:29     ` Andy Shevchenko
2017-12-29 15:48 ` Alexander Tsoy
2017-12-29 15:52   ` Toralf Förster
2017-12-29 20:12 ` Linus Torvalds
2017-12-29 20:21   ` Ingo Molnar
2017-12-29 21:02   ` Toralf Förster
2017-12-29 21:17     ` Linus Torvalds
2017-12-29 21:39       ` Linus Torvalds
2017-12-29 22:04         ` Alexander Tsoy
2017-12-29 22:30       ` Toralf Förster
2017-12-29 22:53         ` Linus Torvalds
2017-12-29 23:14           ` Toralf Förster
2017-12-30  0:10           ` Andy Lutomirski
2017-12-30  1:00             ` Linus Torvalds
2017-12-30  1:34               ` Linus Torvalds
2017-12-30  9:14                 ` Alexander Tsoy
2017-12-30  9:21                   ` Toralf Förster
2017-12-30  1:13             ` Alexander Tsoy
2017-12-30 12:58               ` Toralf Förster
2017-12-30 13:14                 ` Jiri Kosina
2017-12-30  3:49             ` Josh Poimboeuf [this message]
2017-12-30  8:45               ` Alexander Tsoy
2017-12-30 17:09                 ` Josh Poimboeuf
2017-12-30 17:57                   ` Josh Poimboeuf
2017-12-30 22:03                     ` Alexander Tsoy
2017-12-30 22:16                       ` Josh Poimboeuf
2017-12-30  9:30               ` Toralf Förster
2017-12-30  8:32             ` Toralf Förster
2017-12-30  9:53           ` Jiri Kosina

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=20171230034947.6jgk5t7c7jrl6dwg@treble \
    --to=jpoimboe@redhat.com \
    --cc=alexander@tsoy.me \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=stable@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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

all inboxes | Powered by JetHome®