[kernel?] WARNING: ODEBUG bug in exit_to_user_mode_prepare (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cec24b8b6bb8 Merge tag 'char-misc-6.4-rc1' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12d7cb58280000
kernel config: https://syzkaller.appspot.com/x/.config?x=4b34c6306d2591df
dashboard link: https://syzkaller.appspot.com/bug?extid=186d47dce306ec1d1917
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org lu...@kernel.org pet...@infradead.org tg...@linutronix.de]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fc75c322bf72/disk-cec24b8b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a49a5b8384e4/vmlinux-cec24b8b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/df96040ad091/bzImage-cec24b8b.xz

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

WARNING: CPU: 0 PID: 4442 at lib/debugobjects.c:505 debug_print_object+0x194/0x2c0 lib/debugobjects.c:505
Modules linked in:
CPU: 0 PID: 4442 Comm: udevd Not tainted 6.3.0-syzkaller-09882-gcec24b8b6bb8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:debug_print_object+0x194/0x2c0 lib/debugobjects.c:505
Code: df 48 89 fe 48 c1 ee 03 80 3c 16 00 0f 85 c7 00 00 00 48 8b 14 dd a0 ba a6 8a 50 4c 89 ee 48 c7 c7 60 ae a6 8a e8 8c 8c 37 fd <0f> 0b 58 83 05 86 32 65 0a 01 48 83 c4 20 5b 5d 41 5c 41 5d 41 5e
RSP: 0018:ffffc9000345fcb0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000000
RDX: ffff88807cbb0180 RSI: ffffffff814b0f37 RDI: 0000000000000001
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffffffff8a4dd2a0
R13: ffffffff8aa6b400 R14: ffffc9000345fd78 R15: 0000000000000000
FS: 00007f3df7bd3c80(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020404030 CR3: 000000007cabe000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
debug_object_active_state lib/debugobjects.c:962 [inline]
debug_object_active_state+0x1d6/0x350 lib/debugobjects.c:925
debug_rcu_head_queue kernel/rcu/rcu.h:227 [inline]
__call_rcu_common.constprop.0+0x44/0x7e0 kernel/rcu/tree.c:2612
task_work_run+0x16f/0x270 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop kernel/entry/common.c:171 [inline]
exit_to_user_mode_prepare+0x210/0x240 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:297
do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f3df77170a8
Code: 48 8b 05 83 9d 0d 00 64 c7 00 16 00 00 00 83 c8 ff 48 83 c4 20 5b c3 64 8b 04 25 18 00 00 00 85 c0 75 20 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 76 5b 48 8b 15 51 9d 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffee33891d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f3df77170a8
RDX: fffffffffffffe60 RSI: 000000000000125f RDI: 000000000000000c
RBP: 00005559bdd05430 R08: 00000000ffffffff R09: 094874d51ef24ad6
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffee3389408
R13: 000000000000000c R14: 00005559bcb59fee 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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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