On Tue, Aug 8, 2023 at 12:09 AM syzbot <syzbot+e3705186451a87fd93b8@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > syzbot suspects this issue was fixed by commit: > > commit 125bfc7cd750e68c99f1d446e2c22abea08c237f > Author: Li Nan <linan122@xxxxxxxxxx> > Date: Fri Jun 9 09:43:20 2023 +0000 > > md/raid10: fix the condition to call bio_end_io_acct() > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15c26ba9a80000 > start commit: a901a3568fd2 Merge tag 'iomap-6.5-merge-1' of git://git.ke.. > git tree: upstream > kernel config: https://syzkaller.appspot.com/x/.config?x=f5e1158c5b2f83bb > dashboard link: https://syzkaller.appspot.com/bug?extid=e3705186451a87fd93b8 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12518548a80000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=124ccf70a80000 > > If the result looks correct, please mark the issue as fixed by replying with: > > #syz fix: md/raid10: fix the condition to call bio_end_io_acct() No, that's unrelated. Most likely it's due to https://github.com/google/syzkaller/issues/4117 TL;DR: for bugs that only existed for a very short time syzbot is having problems differentiating between revisions where the bug is not yet introduced and where it's already fixed. > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection >
