On Thu, Jul 13, 2023 at 11:37 AM syzbot <syzbot+2f012b85ac8ce9be92e5@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > syzbot suspects this issue was fixed by commit: > > commit c43784c856483dded7956175b5786e27af6d87f1 > Author: Hans Verkuil <hverkuil-cisco@xxxxxxxxx> > Date: Thu Dec 8 07:51:32 2022 +0000 > > media: v4l2-mem2mem: use vb2_is_streaming() > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17e7d1bca80000 No, that's apparently unrelated. Though I don't see where exactly the bisection went astray.. Likely because the reproducer got quite unreliable at older commits and we made a few false "git bisect good" commands. We will soon start automatically discarding such bisection results: https://github.com/google/syzkaller/pull/4028 > start commit: 4da34b7d175d Merge tag 'thermal-6.1-rc2' of git://git.kern.. > git tree: upstream > kernel config: https://syzkaller.appspot.com/x/.config?x=ea03ca45176080bc > dashboard link: https://syzkaller.appspot.com/bug?extid=2f012b85ac8ce9be92e5 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17834f9a880000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10edf526880000 > > If the result looks correct, please mark the issue as fixed by replying with: > > #syz fix: media: v4l2-mem2mem: use vb2_is_streaming() > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection > > --
