From: Thomas Gleixner <tglx@linutronix.de>
To: 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, Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: WARNING: can't access registers at asm_sysvec_call_function_single
Date: Sun, 13 Sep 2020 23:05:21 +0200 [thread overview]
Message-ID: <87lfhdpeum.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <0000000000002b02cf05aed302f3@google.com>
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...
next prev parent reply other threads:[~2020-09-13 21:06 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 [this message]
2020-09-14 16:49 ` Josh Poimboeuf
2020-09-14 16:51 ` Josh Poimboeuf
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=87lfhdpeum.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=alexandre.chartre@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.