[syzbot] [kernel?] upstream-arm64 test error: INFO: task hung in prepare_namespace

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 59ed70ca3c29 Merge remote-tracking branch 'tglx/devmsi-arm..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=17daa881980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e37fbf116261f0b
dashboard link: https://syzkaller.appspot.com/bug?extid=b2e8737f75941acc4220
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/60815a10a042/disk-59ed70ca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ed29e6661847/vmlinux-59ed70ca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0bc74b03961e/Image-59ed70ca.gz.xz

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

INFO: task swapper/0:1 blocked for more than 143 seconds.
Not tainted 6.10.0-rc5-syzkaller-g59ed70ca3c29 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:swapper/0 state:D stack:0 pid:1 tgid:1 ppid:0 flags:0x0000000c
Call trace:
__switch_to+0x314/0x560 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5408 [inline]
__schedule+0x14ac/0x24d8 kernel/sched/core.c:6745
__schedule_loop kernel/sched/core.c:6822 [inline]
schedule+0xbc/0x238 kernel/sched/core.c:6837
wait_for_device_probe+0x120/0x1c0 drivers/base/dd.c:772
prepare_namespace+0x5c/0x11c init/do_mounts.c:479
kernel_init_freeable+0x360/0x478 init/main.c:1591
kernel_init+0x24/0x2a0 init/main.c:1467
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860

Showing all locks held in the system:
1 lock held by khungtaskd/31:
#0: ffff80008f3879e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:328
2 locks held by kworker/u8:2/42:
#0: ffff0000c0031148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x624/0x15b8 kernel/workqueue.c:3205
#1: ffff800095677c20 ((work_completion)(&(&kfence_timer)->work)){+.+.}-{0:0}, at: process_one_work+0x6a0/0x15b8 kernel/workqueue.c:3205
3 locks held by kworker/u8:4/210:
#0: ffff0000c181d148 ((wq_completion)async){+.+.}-{0:0}, at: process_one_work+0x624/0x15b8 kernel/workqueue.c:3205
#1: ffff800098157c20 ((work_completion)(&entry->work)){+.+.}-{0:0}, at: process_one_work+0x6a0/0x15b8 kernel/workqueue.c:3205
#2: ffff0000c2b941b0 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:1009 [inline]
#2: ffff0000c2b941b0 (&dev->mutex){....}-{3:3}, at: __device_driver_lock drivers/base/dd.c:1093 [inline]
#2: ffff0000c2b941b0 (&dev->mutex){....}-{3:3}, at: __driver_attach_async_helper+0xc8/0x230 drivers/base/dd.c:1143
1 lock held by hwrng/1371:
#0: ffff800090aef948 (reading_mutex){+.+.}-{3:3}, at: hwrng_fillfn+0x6c/0x2b4 drivers/char/hw_random/core.c:495

=============================================



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