[v5.15] kernel BUG in diUnmount

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 09996673e313 Linux 5.15.123
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16acca09a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f9d4431ce682ac7e
dashboard link: https://syzkaller.appspot.com/bug?extid=9b79cdd82710053dcd3b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1360d931a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10e5d955a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e665cef1f596/disk-09996673.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c21eeab4b038/vmlinux-09996673.xz
kernel image: https://storage.googleapis.com/syzbot-assets/15e2b5a7aa32/bzImage-09996673.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/18a34177a1da/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9b79cd...@syzkaller.appspotmail.com

do_remount fs/namespace.c:2656 [inline]
path_mount+0xceb/0x10a0 fs/namespace.c:3316
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
------------[ cut here ]------------
kernel BUG at mm/slub.c:3532!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3501 Comm: syz-executor107 Not tainted 5.15.123-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
RIP: 0010:free_nonslab_page+0x14d/0x150 mm/slub.c:3532
Code: e9 41 ff ff ff 48 89 df 48 c7 c6 20 27 14 8c e8 09 12 ed ff 0f 0b e8 b2 2e 53 08 48 89 df 48 c7 c6 51 ac 15 8c e8 f3 11 ed ff <0f> 0b 90 53 48 89 fb e8 b7 0d 83 ff 48 89 df e8 df eb ff ff e8 6a
RSP: 0018:ffffc90002c6fae8 EFLAGS: 00010246
RAX: 9ebcd7a6e3757300 RBX: ffffea0000586e00 RCX: ffff888016a00000
RDX: 0000000000000000 RSI: 000000000000ffff RDI: 000000000000ffff
RBP: ffffea0000586e00 R08: ffffffff81d03784 R09: fffff5200058de19
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888072ec2960
R13: dffffc0000000000 R14: 0000000000000000 R15: ffffea0000586e00
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fed5b613000 CR3: 0000000023336000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kfree+0x1cf/0x270 mm/slub.c:4556
diUnmount+0xef/0x100 fs/jfs/jfs_imap.c:195
jfs_umount+0x109/0x370 fs/jfs/jfs_umount.c:63
jfs_put_super+0x86/0x180 fs/jfs/super.c:194
generic_shutdown_super+0x136/0x2c0 fs/super.c:475
kill_block_super+0x7a/0xe0 fs/super.c:1405
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
__do_sys_exit_group kernel/exit.c:1005 [inline]
__se_sys_exit_group kernel/exit.c:1003 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fed62d245f9
Code: Unable to access opcode bytes at RIP 0x7fed62d245cf.
RSP: 002b:00007fffd7d723f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fed62d245f9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007fed62da3370 R08: ffffffffffffffb8 R09: 00007fed0000000c
R10: 0000000000402020 R11: 0000000000000246 R12: 00007fed62da3370
R13: 0000000000000000 R14: 00007fed62da5140 R15: 00007fed62ceaa00
</TASK>
Modules linked in:
---[ end trace b35267c4b7b1e96a ]---
RIP: 0010:free_nonslab_page+0x14d/0x150 mm/slub.c:3532
Code: e9 41 ff ff ff 48 89 df 48 c7 c6 20 27 14 8c e8 09 12 ed ff 0f 0b e8 b2 2e 53 08 48 89 df 48 c7 c6 51 ac 15 8c e8 f3 11 ed ff <0f> 0b 90 53 48 89 fb e8 b7 0d 83 ff 48 89 df e8 df eb ff ff e8 6a
RSP: 0018:ffffc90002c6fae8 EFLAGS: 00010246
RAX: 9ebcd7a6e3757300 RBX: ffffea0000586e00 RCX: ffff888016a00000
RDX: 0000000000000000 RSI: 000000000000ffff RDI: 000000000000ffff
RBP: ffffea0000586e00 R08: ffffffff81d03784 R09: fffff5200058de19
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888072ec2960
R13: dffffc0000000000 R14: 0000000000000000 R15: ffffea0000586e00
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fed5b613000 CR3: 0000000023336000 CR4: 00000000003506f0
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 syzk...@googlegroups.com.

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

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

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.

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

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

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

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit 6e2bda2c192d0244b5a78b787ef20aa10cb319b7
git tree: upstream
Author: Liu Shixin via Jfs-discussion <jfs-dis...@lists.sourceforge.net>
Date: Thu Dec 1 12:46:28 2022 +0000

jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13bdc196680000

kernel config: https://syzkaller.appspot.com/x/.config?x=f9d4431ce682ac7e
dashboard link: https://syzkaller.appspot.com/bug?extid=9b79cdd82710053dcd3b

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1360d931a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10e5d955a80000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection