Messages in this thread | | | Date | Tue, 11 Oct 2022 07:57:23 -0700 | Subject | Re: [syzbot] KASAN: use-after-free Read in move_expired_inodes (2) | From | syzbot <> |
| |
syzbot has bisected this issue to:
commit cbfecb927f429a6fa613d74b998496bd71e4438a Author: Lukas Czerner <lczerner@redhat.com> Date: Thu Aug 25 10:06:57 2022 +0000
fs: record I_DIRTY_TIME even if inode already has I_DIRTY_INODE
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17e93452880000 start commit: 493ffd6605b2 Merge tag 'ucount-rlimits-cleanups-for-v5.19'.. git tree: upstream final oops: https://syzkaller.appspot.com/x/report.txt?x=14193452880000 console output: https://syzkaller.appspot.com/x/log.txt?x=10193452880000 kernel config: https://syzkaller.appspot.com/x/.config?x=d19f5d16783f901 dashboard link: https://syzkaller.appspot.com/bug?extid=6ba92bd00d5093f7e371 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1724028a880000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17419234880000
Reported-by: syzbot+6ba92bd00d5093f7e371@syzkaller.appspotmail.com Fixes: cbfecb927f42 ("fs: record I_DIRTY_TIME even if inode already has I_DIRTY_INODE")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
| |