All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+c74f40907a9c0479af10@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, kvm@vger.kernel.org,
	 linux-kernel@vger.kernel.org, pbonzini@redhat.com,
	seanjc@google.com,  syzkaller-bugs@googlegroups.com,
	tintinm2017@gmail.com,  usama.anjum@collabora.com
Subject: Re: [syzbot] [kvm?] WARNING in kvm_mmu_notifier_invalidate_range_start (3)
Date: Tue, 05 Mar 2024 05:59:02 -0800	[thread overview]
Message-ID: <0000000000009a8bce0612ea3e3c@google.com> (raw)
In-Reply-To: <000000000000376d93060a5207ed@google.com>

syzbot suspects this issue was fixed by commit:

commit 4cccb6221cae6d020270606b9e52b1678fc8b71a
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Tue Jan 9 11:24:42 2024 +0000

    fs/proc/task_mmu: move mmu notification mechanism inside mm lock

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1638c66c180000
start commit:   b57b17e88bf5 Merge tag 'parisc-for-6.7-rc1-2' of git://git..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=d950a2e2e34359e2
dashboard link: https://syzkaller.appspot.com/bug?extid=c74f40907a9c0479af10
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15785fc4e80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1469c9a8e80000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: fs/proc/task_mmu: move mmu notification mechanism inside mm lock

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2024-03-05 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17  5:01 [syzbot] [kvm?] WARNING in kvm_mmu_notifier_invalidate_range_start (3) syzbot
2023-11-17 10:55 ` [syzbot] Test syzbot
2024-03-05 13:59 ` syzbot [this message]
2024-03-05 15:49   ` [syzbot] [kvm?] WARNING in kvm_mmu_notifier_invalidate_range_start (3) Sean Christopherson
     [not found] <CAJjsb4q_f5EL64d-Cuipk0Vr9aqK2-NtV_NToMnx67yDdxzydg@mail.gmail.com>
2023-11-17 11:21 ` syzbot

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=0000000000009a8bce0612ea3e3c@google.com \
    --to=syzbot+c74f40907a9c0479af10@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tintinm2017@gmail.com \
    --cc=usama.anjum@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.