[v6.1] WARNING: ODEBUG bug in generic_shutdown_super (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 909ba1f1b414 Linux 6.1.90
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1119a590980000
kernel config: https://syzkaller.appspot.com/x/.config?x=3be6d6f79b879a67
dashboard link: https://syzkaller.appspot.com/bug?extid=9f4e5c6733670beb6dbb
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/63178de7cba7/disk-909ba1f1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/25dec90d8126/vmlinux-909ba1f1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/25509ea1c6cd/bzImage-909ba1f1.xz

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

------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: timer_list hint: print_daily_error_info+0x0/0x490
WARNING: CPU: 1 PID: 4199 at lib/debugobjects.c:517 debug_print_object lib/debugobjects.c:514 [inline]
WARNING: CPU: 1 PID: 4199 at lib/debugobjects.c:517 __debug_check_no_obj_freed lib/debugobjects.c:978 [inline]
WARNING: CPU: 1 PID: 4199 at lib/debugobjects.c:517 debug_check_no_obj_freed+0x38e/0x4e0 lib/debugobjects.c:1008
Modules linked in:
CPU: 1 PID: 4199 Comm: syz-executor.0 Not tainted 6.1.90-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:debug_print_object lib/debugobjects.c:514 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:978 [inline]
RIP: 0010:debug_check_no_obj_freed+0x38e/0x4e0 lib/debugobjects.c:1008
Code: ef e8 76 0c a5 fd 4c 8b 45 00 48 c7 c7 40 4d 3d 8b 48 c7 c6 00 4a 3d 8b 48 c7 c2 a0 4e 3d 8b 8b 0c 24 49 89 d9 e8 12 94 15 fd <0f> 0b ff 05 c2 be 36 0a 48 83 c5 30 48 89 e8 48 c1 e8 03 48 b9 00
RSP: 0018:ffffc9000316fa80 EFLAGS: 00010246
RAX: 63158f5656dddd00 RBX: ffffffff824a6780 RCX: ffff888078c78000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffffff8aedd900 R08: ffffffff81528ede R09: fffff5200062deb1
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801f928698
R13: ffffffff91f35ab0 R14: ffff88801f929000 R15: ffff888056a11d78
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c001472000 CR3: 000000005fa20000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1699 [inline]
slab_free_freelist_hook mm/slub.c:1750 [inline]
slab_free mm/slub.c:3661 [inline]
__kmem_cache_free+0x205/0x3c0 mm/slub.c:3674
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7a/0xe0 fs/super.c:1459
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xa73/0x26a0 kernel/exit.c:869
do_group_exit+0x202/0x2b0 kernel/exit.c:1019
__do_sys_exit_group kernel/exit.c:1030 [inline]
__se_sys_exit_group kernel/exit.c:1028 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1028
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f6402c7dca9
Code: Unable to access opcode bytes at 0x7f6402c7dc7f.
RSP: 002b:00007ffd2c0e3768 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f6402cc843d RCX: 00007f6402c7dca9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000027 R08: 00007ffd2c0e1506 R09: 00007ffd2c0e4a20
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd2c0e4a20
R13: 00007f6402cc83b9 R14: 00005555571db430 R15: 000000000000000e
</TASK>


---
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 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