[v6.6] WARNING in kcov_remote_start

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: eac8889a3a1c Linux 6.6.140
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10a5e47e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5b35c4db8465904
dashboard link: https://syzkaller.appspot.com/bug?extid=a0da97bbf72cfbc5a796
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fb5539a09d8e/disk-eac8889a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9b3a1bf56c30/vmlinux-eac8889a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/260b151a96c7/bzImage-eac8889a.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 17041 at kernel/kcov.c:870 arch_local_irq_restore arch/x86/include/asm/irqflags.h:138 [inline]
WARNING: CPU: 0 PID: 17041 at kernel/kcov.c:870 kcov_remote_start+0x551/0x7e0 kernel/kcov.c:888
Modules linked in:
CPU: 0 PID: 17041 Comm: syz.0.3779 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:kcov_remote_start+0x551/0x7e0 kernel/kcov.c:870
Code: ff ff 4c 89 ff be 03 00 00 00 e8 ba 13 a3 02 e9 f0 fa ff ff e8 30 b6 ff 08 f7 c3 00 02 00 00 0f 84 df fa ff ff e9 5a fc ff ff <0f> 0b e8 08 cb ff 08 89 c0 48 c7 c7 00 c3 02 00 48 03 3c c5 30 9a
RSP: 0018:ffffc9000c67f470 EFLAGS: 00010002
RAX: 0000000080000200 RBX: 0000000000000246 RCX: 0000000000000002
RDX: 0000000000000002 RSI: ffffffff8acadd60 RDI: ffffffff8b1c9860
RBP: ffffc9000c67f710 R08: dffffc0000000000 R09: 1ffffffff2238ead
R10: dffffc0000000000 R11: fffffbfff2238eae R12: ffff8880b8e2c300
R13: ffffffff8187301f R14: ffff888022f3bc00 R15: 0000000000000000
FS: 00007fbe0e4726c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff71ecb9440 CR3: 0000000075708000 CR4: 00000000003506f0
DR0: 0000200000000300 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
kcov_remote_start_common include/linux/kcov.h:50 [inline]
ieee80211_rx_list+0x813/0x32d0 net/mac80211/rx.c:5419
ieee80211_rx_napi+0x1b2/0x3d0 net/mac80211/rx.c:5460
ieee80211_rx include/net/mac80211.h:4971 [inline]
ieee80211_handle_queued_frames+0x106/0x1a0 net/mac80211/main.c:319
ieee80211_stop_device+0x2b/0xa0 net/mac80211/util.c:2331
ieee80211_do_stop+0x1707/0x1e20 net/mac80211/iface.c:748
ieee80211_stop+0x436/0x4a0 net/mac80211/iface.c:807
__dev_close_many+0x1d5/0x2b0 net/core/dev.c:1603
__dev_close net/core/dev.c:1615 [inline]
__dev_change_flags+0x2dc/0x6a0 net/core/dev.c:8721
dev_change_flags+0x88/0x1a0 net/core/dev.c:8795
dev_ioctl+0x7b4/0x1140 net/core/dev_ioctl.c:770
sock_do_ioctl+0x239/0x310 net/socket.c:1233
sock_ioctl+0x5ba/0x7e0 net/socket.c:1340
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fbe0d59ce59
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:00007fbe0e472028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fbe0d815fa0 RCX: 00007fbe0d59ce59
RDX: 0000200000000080 RSI: 0000000000008914 RDI: 0000000000000007
RBP: 00007fbe0d632d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fbe0d816038 R14: 00007fbe0d815fa0 R15: 00007ffe55c71768
</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