From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: X86 ML <x86@kernel.org>, Borislav Petkov <bpetkov@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Brian Gerst <brgerst@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 02/16] x86/dumpstack: Add get_stack_info() support for the SYSENTER stack
Date: Mon, 20 Nov 2017 15:27:38 -0600 [thread overview]
Message-ID: <20171120212738.rdevfne2vrruyvt4@treble> (raw)
In-Reply-To: <CALCETrXfo-_ZL60T1vYPmqoimDofGU0OC8LOEaFFh1sVxOLqsw@mail.gmail.com>
On Mon, Nov 20, 2017 at 01:07:16PM -0800, Andy Lutomirski wrote:
> >> but, more importantly, the OOPS unwinder will just bail without this
> >> patch. With the patch, we get a valid unwind, except that everything
> >> has a ? in front.
> >
> > Hm. I can't even fathom how that's possible. Are you talking about the
> > "unwind from NMI to SYSENTER stack" path? Or any unwind to a syscall?
> > Either way I'm baffled... If the unwinder only encounters the SYSENTER
> > stack at the end, how could that cause everything beforehand to have a
> > question mark?
>
> I mean that, if I put a ud2 or other bug in the code that runs on the
> SYSENTER stack, without this patch, I get a totally blank call trace.
I would expect a blank call trace either way...
In fact I just added a ud1 after your RDI save, and got a blank call
trace.
Also the RIP printout isn't very helpful, I guess kallsyms doesn't know
about the trampoline?
[ 2.816226] invalid opcode: 0000 [#10] PREEMPT SMP
[ 2.816968] Modules linked in:
[ 2.817097] CPU: 3 PID: 167 Comm: modprobe Tainted: G D W 4.14.0+ #6
[ 2.817097] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1.fc26 04/01/2014
[ 2.817097] task: ffff88013388c000 task.stack: ffffc9000119c000
[ 2.817097] RIP: 0010:0xffffffffff54a01f
[ 2.817097] RSP: 0018:ffffc9000119ffd0 EFLAGS: 00010046
[ 2.817097] RAX: 000000000000000c RBX: 0000000000000001 RCX: 00007f16fdcf1c89
[ 2.817097] RDX: 00007ffc0b80f030 RSI: 0000561065557480 RDI: 0000000000000000
[ 2.817097] RBP: 0000561065554040 R08: 0000000000000001 R09: 00007ffc0b80f059
[ 2.817097] R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000009
[ 2.817097] R13: 00007f16fdcd9190 R14: 0000000000000001 R15: 0000000000001000
[ 2.817097] FS: 0000000000000000(0000) GS:ffff88013ac00000(0000) knlGS:0000000000000000
[ 2.817097] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2.817097] CR2: 00007f16fdefe0c0 CR3: 0000000133c79004 CR4: 00000000001606e0
[ 2.817097] Call Trace:
[ 2.817097] Code: 00 00 00 00 00 00 00 00 00 00 00 00 0f 01 f8 48 89 25 f6 d1 ff ff 48 8b 25 03 d2 ff ff 6a 2b ff 35 e7 d1 ff ff 41 53 6a 33 51 57 <0f> b9 48 c7 c7 90 6f 92 81 ff e7 90 90 90 90 90 90 90 90 90 90
[ 2.817097] RIP: 0xffffffffff54a01f RSP: ffffc9000119ffd0
[ 2.817097] ---[ end trace 215b2a1d93232ed1 ]---
--
Josh
next prev parent reply other threads:[~2017-11-20 21:27 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 17:07 [PATCH 00/16] Entry stuff, in decent shape now Andy Lutomirski
2017-11-20 17:07 ` [PATCH 01/16] x86/asm/64: Allocate and enable the SYSENTER stack Andy Lutomirski
2017-11-20 21:55 ` Thomas Gleixner
2017-11-21 10:47 ` Borislav Petkov
2017-11-20 17:07 ` [PATCH 02/16] x86/dumpstack: Add get_stack_info() support for " Andy Lutomirski
2017-11-20 20:42 ` Josh Poimboeuf
2017-11-20 20:46 ` Andy Lutomirski
2017-11-20 21:00 ` Josh Poimboeuf
2017-11-20 21:07 ` Andy Lutomirski
2017-11-20 21:27 ` Josh Poimboeuf [this message]
2017-11-20 21:30 ` Andy Lutomirski
2017-11-20 21:55 ` Josh Poimboeuf
2017-11-21 1:39 ` Andy Lutomirski
2017-11-21 2:29 ` Josh Poimboeuf
2017-11-20 17:07 ` [PATCH 03/16] x86/gdt: Put per-cpu GDT remaps in ascending order Andy Lutomirski
2017-11-20 21:56 ` Thomas Gleixner
2017-11-21 17:16 ` Borislav Petkov
2017-11-20 17:07 ` [PATCH 04/16] x86/fixmap: Generalize the GDT fixmap mechanism Andy Lutomirski
2017-11-20 22:01 ` Thomas Gleixner
2017-11-21 1:21 ` Andy Lutomirski
2017-11-21 8:29 ` Thomas Gleixner
2017-11-20 17:07 ` [PATCH 05/16] x86/asm: Fix assumptions that the HW TSS is at the beginning of cpu_tss Andy Lutomirski
2017-11-20 22:22 ` Thomas Gleixner
2017-11-20 17:07 ` [PATCH 06/16] x86/dumpstack: Handle stack overflow on all stacks Andy Lutomirski
2017-11-20 17:07 ` [PATCH 07/16] x86/asm: Move SYSENTER_stack to the beginning of struct tss_struct Andy Lutomirski
2017-11-20 23:37 ` Thomas Gleixner
2017-11-21 1:25 ` Andy Lutomirski
2017-11-20 17:07 ` [PATCH 08/16] x86/asm: Remap the TSS into the cpu entry area Andy Lutomirski
2017-11-20 17:07 ` [PATCH 09/16] x86/asm/64: Separate cpu_current_top_of_stack from TSS.sp0 Andy Lutomirski
2017-11-20 17:07 ` [PATCH 10/16] x86/espfix/64: Stop assuming that pt_regs is on the entry stack Andy Lutomirski
2017-11-20 17:07 ` [PATCH 11/16] x86/asm/64: Use a percpu trampoline stack for IDT entries Andy Lutomirski
2017-11-21 7:20 ` Ingo Molnar
2017-11-21 15:36 ` Andy Lutomirski
2017-11-21 18:57 ` Dave Hansen
2017-11-22 3:45 ` Andy Lutomirski
2017-11-20 17:07 ` [PATCH 12/16] x86/asm/64: Return to userspace from the trampoline stack Andy Lutomirski
2017-11-20 17:07 ` [PATCH 13/16] x86/entry/64: Create a percpu SYSCALL entry trampoline Andy Lutomirski
2017-11-21 2:34 ` Josh Poimboeuf
2017-11-21 3:20 ` Andy Lutomirski
2017-11-20 17:07 ` [PATCH 14/16] x86/irq: Remove an old outdated comment about context tracking races Andy Lutomirski
2017-11-21 6:25 ` Ingo Molnar
2017-11-20 17:07 ` [PATCH 15/16] x86/irq/64: In the stack overflow warning, print the offending IP Andy Lutomirski
2017-11-21 6:26 ` Ingo Molnar
2017-11-20 17:07 ` [PATCH 16/16] x86/entry/64: Move the IST stacks into cpu_entry_area Andy Lutomirski
2017-11-21 7:38 ` Ingo Molnar
2017-11-21 14:45 ` Andrey Ryabinin
2017-11-23 15:25 ` Andy Lutomirski
2017-11-21 15:33 ` Andy Lutomirski
2017-11-20 18:48 ` [PATCH 00/16] Entry stuff, in decent shape now Andy Lutomirski
2017-11-21 7:33 ` Ingo Molnar
2017-11-21 15:59 ` Andy Lutomirski
2017-11-21 16:12 ` Andy Lutomirski
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=20171120212738.rdevfne2vrruyvt4@treble \
--to=jpoimboe@redhat.com \
--cc=bpetkov@suse.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--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
Powered by JetHome