From: Thomas Gleixner <tglx@linutronix.de>
To: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+dc1fa714cb070b184db5@syzkaller.appspotmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
the arch/x86 maintainers <x86@kernel.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: PANIC: double fault in fixup_bad_iret
Date: Fri, 29 May 2020 17:57:10 +0200 [thread overview]
Message-ID: <87o8q6n38p.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CACT4Y+ajjB8RmG3_H_9r-kaRAZ05ejW02-Py47o7wkkBjwup3Q@mail.gmail.com>
Dmitry,
Dmitry Vyukov <dvyukov@google.com> writes:
> On Fri, May 29, 2020 at 3:14 PM syzbot
> <syzbot+dc1fa714cb070b184db5@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit: 7b4cb0a4 Add linux-next specific files for 20200525
>> git tree: linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=15dc34ba100000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=47b0740d89299c10
>> dashboard link: https://syzkaller.appspot.com/bug?extid=dc1fa714cb070b184db5
>> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14678626100000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1017ef06100000
>>
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by: syzbot+dc1fa714cb070b184db5@syzkaller.appspotmail.com
>
> From the reproducer it seems to be either x86 related or ptrace
> related.
>
>> RIP: 0010:fixup_bad_iret+0x24/0x170 arch/x86/kernel/traps.c:665
as a quick assumption that's related to KASAN in fixup_bad_iret() which
is a frightenly bad idea. I'm about to verify.
Thanks,
tglx
next prev parent reply other threads:[~2020-05-29 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 13:14 PANIC: double fault in fixup_bad_iret syzbot
2020-05-29 13:20 ` Dmitry Vyukov
2020-05-29 15:57 ` Thomas Gleixner [this message]
2020-05-29 16:06 ` Thomas Gleixner
2020-05-29 16:07 ` Peter Zijlstra
2020-05-29 17:11 ` Peter Zijlstra
2020-05-30 7:39 ` Thomas Gleixner
2020-05-31 9:32 ` Dmitry Vyukov
2020-06-01 12:40 ` Marco Elver
2020-06-02 9:41 ` Peter Zijlstra
2020-06-02 17:51 ` Marco Elver
2020-06-02 17:58 ` Peter Zijlstra
2020-06-15 22:31 ` [tip: x86/entry] kasan: Bump required compiler version tip-bot2 for Marco Elver
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=87o8q6n38p.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=syzbot+dc1fa714cb070b184db5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox