From: syzbot <syzbot+ceded3495a1d59f2d244@syzkaller.appspotmail.com>
To: hpa@zytor.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
liran.alon@oracle.com, luto@kernel.org, mark.kanda@oracle.com,
mingo@redhat.com, patrick.colp@oracle.com, pbonzini@redhat.com,
rkrcmar@redhat.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: KASAN: use-after-free Read in __schedule (2)
Date: Thu, 07 Nov 2019 05:42:09 -0800 [thread overview]
Message-ID: <000000000000f3131f0596c1d4ed@google.com> (raw)
In-Reply-To: <0000000000000cc0de0572736043@google.com>
syzbot suspects this bug was fixed by commit:
commit 26b471c7e2f7befd0f59c35b257749ca57e0ed70
Author: Liran Alon <liran.alon@oracle.com>
Date: Sun Sep 16 11:28:20 2018 +0000
KVM: nVMX: Fix bad cleanup on error of get/set nested state IOCTLs
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14830572600000
start commit: 234b69e3 ocfs2: fix ocfs2 read block panic
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=5fa12be50bca08d8
dashboard link: https://syzkaller.appspot.com/bug?extid=ceded3495a1d59f2d244
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1634bbae400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1728324e400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: KVM: nVMX: Fix bad cleanup on error of get/set nested state IOCTLs
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2019-11-07 13:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000000cc0de0572736043@google.com>]
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=000000000000f3131f0596c1d4ed@google.com \
--to=syzbot+ceded3495a1d59f2d244@syzkaller.appspotmail.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=luto@kernel.org \
--cc=mark.kanda@oracle.com \
--cc=mingo@redhat.com \
--cc=patrick.colp@oracle.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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