On Wed, 1 Feb 2023 at 00:05, syzbot <syzbot+deb631beeb93bdb2df4c@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > syzbot suspects this issue was fixed by commit: > > commit c380b52f6c5702cc4bdda5e6d456d6c19a201a0b > Author: Konstantin Komarov <almaz.alexandrovich@xxxxxxxxxxxxxxxxxxxx> > Date: Fri Oct 7 11:02:36 2022 +0000 > > fs/ntfs3: Change new sparse cluster processing > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1377b979480000 > start commit: e2ca6ba6ba01 Merge tag 'mm-stable-2022-12-13' of git://git.. > git tree: upstream > kernel config: https://syzkaller.appspot.com/x/.config?x=276eb8ff64eb2c27 > dashboard link: https://syzkaller.appspot.com/bug?extid=deb631beeb93bdb2df4c > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10d8601b880000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a09c93880000 > > If the result looks correct, please mark the issue as fixed by replying with: > > #syz fix: fs/ntfs3: Change new sparse cluster processing > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection Looks reasonable, let's close the bug so that syzbot reports similar bugs in future: #syz fix: fs/ntfs3: Change new sparse cluster processing
