[moderation] [fs?] WARNING: ODEBUG bug in remove_vm_area

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a446e965a188 Merge tag '6.13-rc2-smb3-client-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1120a730580000
kernel config: https://syzkaller.appspot.com/x/.config?x=99a5586995ec03b2
dashboard link: https://syzkaller.appspot.com/bug?extid=b3a987c3a8f43b42ebb1
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c587fa5f3f1f/disk-a446e965.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9144082eb502/vmlinux-a446e965.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8946168082ea/bzImage-a446e965.xz

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

------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff88806f482708 object type: timer_list hint: addrconf_rs_timer+0x0/0x840 include/net/addrconf.h:330
WARNING: CPU: 1 PID: 5825 at lib/debugobjects.c:612 debug_print_object+0x1a2/0x2b0 lib/debugobjects.c:612
Modules linked in:
CPU: 1 UID: 0 PID: 5825 Comm: syz-executor Not tainted 6.13.0-rc2-syzkaller-00292-ga446e965a188 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
RIP: 0010:debug_print_object+0x1a2/0x2b0 lib/debugobjects.c:612
Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 54 48 8b 14 dd e0 68 b1 8b 41 56 4c 89 e6 48 c7 c7 60 5d b1 8b e8 0f 53 bc fc 90 <0f> 0b 90 90 58 83 05 36 38 7f 0b 01 48 83 c4 18 5b 5d 41 5c 41 5d
RSP: 0018:ffffc90003e5f9e8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffffff815a16c9
RDX: ffff888030de5a00 RSI: ffffffff815a16d6 RDI: 0000000000000001
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffffffff8bb16400
R13: ffffffff8b4f8020 R14: ffffffff89cb65c0 R15: ffffc90003e5faf8
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007febe3ea7d60 CR3: 000000002a360000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__debug_check_no_obj_freed lib/debugobjects.c:1099 [inline]
debug_check_no_obj_freed+0x4b7/0x600 lib/debugobjects.c:1129
remove_vm_area+0x1ae/0x3f0 mm/vmalloc.c:3241
vfree+0x90/0x890 mm/vmalloc.c:3364
kvfree+0x33/0x50 mm/util.c:691
vfree+0x333/0x890 mm/vmalloc.c:3386
kcov_put kernel/kcov.c:439 [inline]
kcov_put+0x2a/0x40 kernel/kcov.c:435
kcov_close+0xd/0x20 kernel/kcov.c:535
__fput+0x3f8/0xb60 fs/file_table.c:450
task_work_run+0x14e/0x250 kernel/task_work.c:239
exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0xadd/0x2d70 kernel/exit.c:938
do_group_exit+0xd3/0x2a0 kernel/exit.c:1087
__do_sys_exit_group kernel/exit.c:1098 [inline]
__se_sys_exit_group kernel/exit.c:1096 [inline]
__x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1096
x64_sys_call+0x151f/0x1720 arch/x86/include/generated/asm/syscalls_64.h:232
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff280585d19
Code: Unable to access opcode bytes at 0x7ff280585cef.
RSP: 002b:00007ffc56ab7368 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 00007ff280585d19
RDX: 00007ff280584790 RSI: 0000000000000004 RDI: 0000000000000007
RBP: 00007ff280776738 R08: 00007ffc56ab5107 R09: 0000000000000008
R10: 0000000000000019 R11: 0000000000000246 R12: 0000000000000008
R13: 0000000000000003 R14: 0000000000000009 R15: 0000000000000000
</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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.