mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+b6ccd31787585244a855@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, fmdefrancesco@gmail.com,
	ira.weiny@intel.com,  linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,  pbonzini@redhat.com,
	seanjc@google.com, slava@dubeyko.com,
	 syzkaller-bugs@googlegroups.com, yongwei.ma@intel.com
Subject: Re: [syzbot] [hfs?] possible deadlock in hfsplus_block_allocate
Date: Thu, 14 Mar 2024 01:20:03 -0700	[thread overview]
Message-ID: <000000000000e3d63206139a8e1a@google.com> (raw)
In-Reply-To: <0000000000009c31e605ee9c1a13@google.com>

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

      parent reply	other threads:[~2024-03-14  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 13:38 [syzbot] " syzbot
2024-03-13 22:37 ` [syzbot] [hfs?] " syzbot
2024-03-14  8:20 ` syzbot [this message]

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=000000000000e3d63206139a8e1a@google.com \
    --to=syzbot+b6ccd31787585244a855@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fmdefrancesco@gmail.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=slava@dubeyko.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yongwei.ma@intel.com \
    /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
Powered by JetHome