[v5.15] INFO: task hung in devlink_pernet_pre_exit (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1c700860e8bc Linux 5.15.185
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=174c6a82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=db74c56dea20051
dashboard link: https://syzkaller.appspot.com/bug?extid=983c422144d245941785
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c9bcd8fb21/disk-1c700860.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/75eaa3b1c3f3/vmlinux-1c700860.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ed251e9d15fe/bzImage-1c700860.xz

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

INFO: task syz-executor:7621 blocked for more than 143 seconds.
Not tainted 5.15.185-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:23744 pid: 7621 ppid: 1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x11b8/0x43b0 kernel/sched/core.c:6376
schedule+0x11b/0x1e0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xc71/0x2390 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
devlink_pernet_pre_exit+0x97/0x300 net/core/devlink.c:11534


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