Re: [syzbot] [jfs?] KASAN: user-memory-access Write in __destroy_inode

[Mateusz Guzik]

On Wed, Jan 7, 2026 at 3:57 PM syzbot
<syzbot+dcc068159182a4c31ca3@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit dca3aa666fbd71118905d88bb1c353881002b647
> Author: Mateusz Guzik <mjguzik@xxxxxxxxx>
> Date:   Sun Nov 9 12:19:31 2025 +0000
>
>     fs: move inode fields used during fast path lookup closer together
>

I don't know what the bug is, at best this patch has an unintended
side-effect of neutering the reproducer.

> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1480019a580000
> start commit:   6146a0f1dfae Linux 6.18-rc4
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=e46b8a1c645465a9
> dashboard link: https://syzkaller.appspot.com/bug?extid=dcc068159182a4c31ca3
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15ef4532580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=179c1e14580000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: fs: move inode fields used during fast path lookup closer together
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection