On Sun, Mar 31, 2019 at 02:08:00AM -0700, syzbot wrote: > syzbot has bisected this bug to: > > commit 8fcc4b5923af5de58b80b53a069453b135693304 > Author: Jim Mattson <jmattson@xxxxxxxxxx> > Date: Tue Jul 10 09:27:20 2018 +0000 > > kvm: nVMX: Introduce KVM_CAP_NESTED_STATE > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=127b4f43200000 > start commit: 234b69e3 ocfs2: fix ocfs2 read block panic > git tree: upstream > final crash: https://syzkaller.appspot.com/x/report.txt?x=117b4f43200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=167b4f43200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=5fa12be50bca08d8 > dashboard link: https://syzkaller.appspot.com/bug?extid=1c69d94fe42901b029c1 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e14956400000 > > Reported-by: syzbot+1c69d94fe42901b029c1@xxxxxxxxxxxxxxxxxxxxxxxxx > Fixes: 8fcc4b5923af ("kvm: nVMX: Introduce KVM_CAP_NESTED_STATE") > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection Another ancient bug, fixed by commit 26b471c7e2f7 ("KVM: nVMX: Fix bad cleanup on error of get/set nested state IOCTLs") #syz fix: KVM: nVMX: Fix bad cleanup on error of get/set nested state IOCTLs
