[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Zec_J7VKp_4QAP0Z@google.com>
Date: Tue, 5 Mar 2024 07:49:59 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: syzbot <syzbot+c74f40907a9c0479af10@...kaller.appspotmail.com>
Cc: akpm@...ux-foundation.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, pbonzini@...hat.com,
syzkaller-bugs@...glegroups.com, tintinm2017@...il.com,
usama.anjum@...labora.com
Subject: Re: [syzbot] [kvm?] WARNING in kvm_mmu_notifier_invalidate_range_start
(3)
On Tue, Mar 05, 2024, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 4cccb6221cae6d020270606b9e52b1678fc8b71a
> Author: Muhammad Usama Anjum <usama.anjum@...labora.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
#syz fix: fs/proc/task_mmu: move mmu notification mechanism inside mm lock
Powered by blists - more mailing lists