Messages in this thread | | | Date | Thu, 14 Mar 2024 01:20:03 -0700 | Subject | Re: [syzbot] [hfs?] possible deadlock in hfsplus_block_allocate | From | syzbot <> |
| |
syzbot has bisected this issue to:
commit 427c76aed29ec12a57f11546a5036df3cc52855e Author: Sean Christopherson <seanjc@google.com> Date: Sat Jul 29 01:35:32 2023 +0000
KVM: x86/mmu: Bug the VM if write-tracking is used but not enabled
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1779a8c9180000 start commit: 61387b8dcf1d Merge tag 'for-6.9/dm-vdo' of git://git.kerne.. git tree: upstream final oops: https://syzkaller.appspot.com/x/report.txt?x=14f9a8c9180000 console output: https://syzkaller.appspot.com/x/log.txt?x=10f9a8c9180000 kernel config: https://syzkaller.appspot.com/x/.config?x=e30ff6b515606856 dashboard link: https://syzkaller.appspot.com/bug?extid=b6ccd31787585244a855 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=129e58c9180000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154b15d6180000
Reported-by: syzbot+b6ccd31787585244a855@syzkaller.appspotmail.com Fixes: 427c76aed29e ("KVM: x86/mmu: Bug the VM if write-tracking is used but not enabled")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
| |