On Tue, Mar 9, 2021 at 12:29 AM 'Sean Christopherson' via
syzkaller-bugs <syzkaller-b...@googlegroups.com> wrote:
>
> On Mon, Mar 08, 2021, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    a38fd874 Linux 5.12-rc2
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=14158fdad00000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=db9c6adb4986f2f2
> > dashboard link: https://syzkaller.appspot.com/bug?extid=3c2bc6358072ede0f11b
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1096d35cd00000
> > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16bf1e52d00000
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+3c2bc6358072ede0f...@syzkaller.appspotmail.com
>
> Wanpeng has a patch posted to fix this[*], is there a way to retroactively 
> point
> syzbot at that fix?
>
> [*] 
> https://lkml.kernel.org/r/1614057902-23774-1-git-send-email-wanpen...@tencent.com

Great! Yes, it can be communicated to syzbot with:

#syz fix: x86/kvm: Fix broken irq restoration in kvm_wait

For details see: http://bit.do/syzbot#communication-with-syzbot

Reply via email to