[Android 6.1] BUG: workqueue lockup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d51e21b39415 ANDROID: ABI: Update pixel symbol list
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=106c7411a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b75c7b7ab5a09aff
dashboard link: https://syzkaller.appspot.com/bug?extid=64286f251ae123d869a5
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=102ad39aa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128c786ea80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/21eb76a46d9a/disk-d51e21b3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5be1b04588af/vmlinux-d51e21b3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/40f71d11f5ca/bzImage-d51e21b3.xz

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

RBP: 00007ffba3c56300 R08: 00007ffba3b8d6c0 R09: 00007ffba3b8d6c0
R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffba3c23074
R13: 0000000000000000 R14: 00007ffd49e3e950 R15: 00007ffd49e3ea38
</TASK>
BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 278s!
BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=-20 stuck for 273s!
Showing busy workqueues and worker pools:
workqueue events: flags=0x0
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256 refcnt=3
in-flight: 19:vmstat_shepherd
pending: psi_avgs_work
workqueue events_unbound: flags=0x2
pwq 4: cpus=0-1 flags=0x4 nice=0 active=2/512 refcnt=4
pending: flush_memcg_stats_dwork, toggle_allocation_gate
workqueue events_power_efficient: flags=0x80
pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=5/256 refcnt=6
pending: neigh_managed_work, neigh_managed_work, neigh_periodic_work, neigh_periodic_work, gc_worker
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
pending: check_lifetime
workqueue mm_percpu_wq: flags=0x8
pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
pending: vmstat_update
pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
pending: vmstat_update
workqueue writeback: flags=0x4a
pwq 4: cpus=0-1 flags=0x4 nice=0 active=1/256 refcnt=3
pending: wb_workfn
workqueue kblockd: flags=0x18
pwq 3: cpus=1 node=0 flags=0x0 nice=-20 active=1/256 refcnt=2
pending: blk_mq_timeout_work
workqueue dm_bufio_cache: flags=0x8
pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
pending: work_fn
workqueue ipv6_addrconf: flags=0x40008
pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/1 refcnt=2
pending: addrconf_verify_work
pool 0: cpus=0 node=0 flags=0x0 nice=0 hung=114s workers=2 idle: 6


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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