[v6.1] INFO: task hung in rtnetlink_rcv_msg

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d23900f974e0 Linux 6.1.55
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=179fda76680000
kernel config: https://syzkaller.appspot.com/x/.config?x=5bcd925baa8f3696
dashboard link: https://syzkaller.appspot.com/bug?extid=3c1b4e500df7b7955c95
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/bdd6d6e750b0/disk-d23900f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a43703f89e81/vmlinux-d23900f9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/30f239dbfd4c/bzImage-d23900f9.xz

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

INFO: task syz-executor.0:19183 blocked for more than 143 seconds.
Not tainted 6.1.55-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:27256 pid:19183 ppid:3571 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
rtnl_lock net/core/rtnetlink.c:74 [inline]
rtnetlink_rcv_msg+0x7c1/0xff0 net/core/rtnetlink.c:6121


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

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