From: syzbot <syzbot+4e78ae6b12b00b9d1042@syzkaller.appspotmail.com>
To: bp@alien8.de, hpa@zytor.com, jmattson@google.com,
joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
pbonzini@redhat.com, peterz@infradead.org,
sean.j.christopherson@intel.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, vkuznets@redhat.com, wanpengli@tencent.com,
will@kernel.org, x86@kernel.org
Subject: Re: WARNING in handle_exception_nmi
Date: Thu, 05 Nov 2020 09:17:08 -0800 [thread overview]
Message-ID: <00000000000014484705b35f4414@google.com> (raw)
In-Reply-To: <000000000000dd392b05b0a1b7ac@google.com>
syzbot suspects this issue was fixed by commit:
commit f8e48a3dca060e80f672d398d181db1298fbc86c
Author: Peter Zijlstra <peterz@infradead.org>
Date: Thu Oct 22 10:23:02 2020 +0000
lockdep: Fix preemption WARN for spurious IRQ-enable
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17bbfa8a500000
start commit: d3d45f82 Merge tag 'pinctrl-v5.9-2' of git://git.kernel.or..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=89ab6a0c48f30b49
dashboard link: https://syzkaller.appspot.com/bug?extid=4e78ae6b12b00b9d1042
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12f24a0b900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167b838f900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: lockdep: Fix preemption WARN for spurious IRQ-enable
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-11-05 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 20:18 WARNING in handle_exception_nmi syzbot
2020-11-05 17:17 ` syzbot [this message]
2020-11-11 11:10 ` Dmitry Vyukov
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=00000000000014484705b35f4414@google.com \
--to=syzbot+4e78ae6b12b00b9d1042@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=will@kernel.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