From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: syzbot <syzbot+bc9dbf05dcc151e9b972@syzkaller.appspotmail.com>,
alexandre.chartre@oracle.com, bp@alien8.de, hpa@zytor.com,
linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
x86@kernel.org
Subject: Re: WARNING: can't access registers at asm_sysvec_call_function_single
Date: Mon, 14 Sep 2020 11:51:13 -0500 [thread overview]
Message-ID: <20200914165113.l5iloshztgykyqxy@treble> (raw)
In-Reply-To: <20200914164927.t476jnlkmdibgqvn@treble>
On Mon, Sep 14, 2020 at 11:49:30AM -0500, Josh Poimboeuf wrote:
> On Sun, Sep 13, 2020 at 11:05:21PM +0200, Thomas Gleixner wrote:
> > On Tue, Sep 08 2020 at 13:16, syzbot wrote:
> >
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit: f4d51dff Linux 5.9-rc4
> > > git tree: upstream
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=1455d4f9900000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=a9075b36a6ae26c9
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=bc9dbf05dcc151e9b972
> > > compiler: gcc (GCC) 10.1.0-syz 20200507
> > >
> > > Unfortunately, I don't have any reproducer for this issue yet.
> > >
> > > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > > Reported-by: syzbot+bc9dbf05dcc151e9b972@syzkaller.appspotmail.com
> > >
> > > WARNING: can't access registers at asm_sysvec_call_function_single+0x12/0x20 arch/x86/include/asm/idtentry.h:589
> >
> > That's the ORC unwinder complaining, but I have no idea why...
>
> 0000000000000cd0 <asm_sysvec_call_function_single>:
> cd0: 90 nop
> cd1: 90 nop
> cd2: 90 nop
> cd3: 6a ff pushq $0xffffffffffffffff
> cd5: e8 b6 03 00 00 callq 1090 <error_entry>
> cda: 48 89 e7 mov %rsp,%rdi
> cdd: e8 00 00 00 00 callq ce2 <asm_sysvec_call_function_single+0x12>
> cde: R_X86_64_PLT32 sysvec_call_function_single-0x4
> ce2: e9 69 04 00 00 jmpq 1150 <error_return>
> ce7: 66 0f 1f 84 00 00 00 nopw 0x0(%rax,%rax,1)
> cee: 00 00
>
> This is a head scratcher. The ORC data looks ok, at least when I build
> it on my system. It's expecting to find pt_regs at the top of the stack
> after returning from sysvec_call_function_single(). But it can't
> dereference the regs for some reason.
>
> So either it's a bug in ORC data or unwinder (not likely) or the stack
> pointer got corrupted somehow (also seems unlikely)...
The true bug may be revealed elsewhere on the stack... I probably need
to start enabling ORC stack dumps like I did for FP.
--
Josh
next prev parent reply other threads:[~2020-09-14 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 20:16 WARNING: can't access registers at asm_sysvec_call_function_single syzbot
2020-09-13 21:05 ` Thomas Gleixner
2020-09-14 16:49 ` Josh Poimboeuf
2020-09-14 16:51 ` Josh Poimboeuf [this message]
2020-09-15 4:27 ` Dmitry Vyukov
2020-09-15 14:19 ` Josh Poimboeuf
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=20200914165113.l5iloshztgykyqxy@treble \
--to=jpoimboe@redhat.com \
--cc=alexandre.chartre@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot+bc9dbf05dcc151e9b972@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).