[v6.1] WARNING in __set_task_frozen

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10b67e32580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=2e6000b56cc7ab3b5817
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9a6fe2a54d0f/disk-fb28aa72.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/742b23a1d931/vmlinux-fb28aa72.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b3f257c16d2e/bzImage-fb28aa72.xz

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

Bluetooth: hci3: Suspend notifier action (3) failed: -4
Freezing user space processes
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4491 at kernel/freezer.c:129 __set_task_frozen+0x1e9/0x290 kernel/freezer.c:129
Modules linked in:
CPU: 1 PID: 4491 Comm: syz.2.43 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:__set_task_frozen+0x1e9/0x290 kernel/freezer.c:129
Code: 68 c7 03 00 80 00 00 bd 00 80 00 00 89 e8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 a3 83 11 00 0f 0b e9 2c ff ff ff e8 97 83 11 00 <0f> 0b eb bf 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 38 fe ff ff 48 89
RSP: 0018:ffffc90005417a50 EFLAGS: 00010087
RAX: ffffffff8170aa89 RBX: ffff88802a9f0018 RCX: 0000000000080000
RDX: ffffc90005819000 RSI: 000000000007f035 RDI: 000000000007f036
RBP: 0000000000000003 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000a82f2c R12: 0000000000000000
R13: 1ffff1100553e003 R14: ffff88802a9f0ad8 R15: dffffc0000000000
FS: 00007f37de9526c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007faf8fd4f880 CR3: 0000000023e82000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
task_call_func+0x19e/0x260 kernel/sched/core.c:4308
__freeze_task kernel/freezer.c:139 [inline]
freeze_task+0x213/0x3a0 kernel/freezer.c:158
try_to_freeze_tasks+0x190/0x600 kernel/power/process.c:54
freeze_processes+0xc5/0x1e0 kernel/power/process.c:137
suspend_freeze_processes kernel/power/power.h:257 [inline]
suspend_prepare kernel/power/suspend.c:372 [inline]
enter_state kernel/power/suspend.c:589 [inline]
pm_suspend+0x289/0x9a0 kernel/power/suspend.c:626
state_store+0x202/0x290 kernel/power/main.c:639
kernfs_fop_write_iter+0x3a0/0x520 fs/kernfs/file.c:352
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x482/0x9a0 fs/read_write.c:584
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f37dd99e019
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f37de952028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f37ddc25fa0 RCX: 00007f37dd99e019
RDX: 0000000000000003 RSI: 0000200000000240 RDI: 0000000000000004
RBP: 00007f37dda3500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f37ddc26038 R14: 00007f37ddc25fa0 R15: 00007ffd843bae78
</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 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