[v5.15] kernel BUG in clear_inode (3)

Hello,

syzbot found the following issue on:

HEAD commit: 0a51d2d4527b Linux 5.15.173
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=118a4ec0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f63d146f1af4415a
dashboard link: https://syzkaller.appspot.com/bug?extid=fd3c895d1c86f6104539
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/733a95526889/disk-0a51d2d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/409603e5dc40/vmlinux-0a51d2d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d60efa369ee/bzImage-0a51d2d4.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
kernel BUG at fs/inode.c:567!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 275 Comm: jfsCommit Not tainted 5.15.173-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:clear_inode+0x12a/0x150 fs/inode.c:567
Code: 0c bb a3 ff 43 80 7c 25 00 00 74 08 4c 89 f7 e8 bc 93 ed ff 49 c7 06 60 00 00 00 5b 41 5c 41 5d 41 5e 41 5f c3 e8 e6 ba a3 ff <0f> 0b e8 df ba a3 ff 0f 0b e8 d8 ba a3 ff 0f 0b e8 d1 ba a3 ff 0f
RSP: 0018:ffffc90002677b08 EFLAGS: 00010093
RAX: ffffffff81dcb8ba RBX: 0000000000000001 RCX: ffff88801e5fd940
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90002677cb0 R08: ffffffff81dcb7e4 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88805f86bde0 R15: ffff88805f86bbb0
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f124d8ec000 CR3: 00000000642cd000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_evict_inode+0xb1/0x440 fs/jfs/inode.c:166
evict+0x529/0x930 fs/inode.c:622
txUpdateMap+0x825/0x9e0 fs/jfs/jfs_txnmgr.c:2401
txLazyCommit fs/jfs/jfs_txnmgr.c:2698 [inline]
jfs_lazycommit+0x470/0xc30 fs/jfs/jfs_txnmgr.c:2766
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace a14c7883e2121268 ]---
RIP: 0010:clear_inode+0x12a/0x150 fs/inode.c:567
Code: 0c bb a3 ff 43 80 7c 25 00 00 74 08 4c 89 f7 e8 bc 93 ed ff 49 c7 06 60 00 00 00 5b 41 5c 41 5d 41 5e 41 5f c3 e8 e6 ba a3 ff <0f> 0b e8 df ba a3 ff 0f 0b e8 d8 ba a3 ff 0f 0b e8 d1 ba a3 ff 0f
RSP: 0018:ffffc90002677b08 EFLAGS: 00010093
RAX: ffffffff81dcb8ba RBX: 0000000000000001 RCX: ffff88801e5fd940
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90002677cb0 R08: ffffffff81dcb7e4 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88805f86bde0 R15: ffff88805f86bbb0
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f124d8ec000 CR3: 00000000642cd000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at [email protected].

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot has found a reproducer for the following issue on:
console output: https://syzkaller.appspot.com/x/log.txt?x=12434ec0580000
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17a1d930580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17dc06e8580000
mounted in repro: https://storage.googleapis.com/syzbot-assets/9adbb9597e9d/mount_0.gz
CPU: 0 PID: 276 Comm: jfsCommit Not tainted 5.15.173-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RSP: 0018:ffffc90002cd7b08 EFLAGS: 00010093
RAX: ffffffff81dcb8ba RBX: 0000000000000001 RCX: ffff88801e9c3b80
RBP: ffffc90002cd7cb0 R08: ffffffff81dcb7e4 R09: 0000000000000003
R13: dffffc0000000000 R14: ffff888070aab4a0 R15: ffff888070aab270
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CR2: 00007ffe42581e08 CR3: 000000001f5b9000 CR4: 00000000003506f0
---[ end trace 192f503931ea8e51 ]---
RSP: 0018:ffffc90002cd7b08 EFLAGS: 00010093
RAX: ffffffff81dcb8ba RBX: 0000000000000001 RCX: ffff88801e9c3b80
RBP: ffffc90002cd7cb0 R08: ffffffff81dcb7e4 R09: 0000000000000003
R13: dffffc0000000000 R14: ffff888070aab4a0 R15: ffff888070aab270
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CR2: 00007ffe42581e08 CR3: 000000001f5b9000 CR4: 00000000003506f0
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.