[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <68b40b55.a70a0220.1c57d1.030a.GAE@google.com>
Date: Sun, 31 Aug 2025 01:44:05 -0700
From: syzbot <syzbot+535bbe83dfc3ae8d4be3@...kaller.appspotmail.com>
To: hdanton@...a.com, krzk@...nel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com, ysk@...lloc.com
Subject: Re: [syzbot] [net?] [nfc?] WARNING in nfc_rfkill_set_block
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in call_timer_fn
------------[ cut here ]------------
workqueue: cannot queue hci_cmd_timeout on wq hci0
WARNING: CPU: 1 PID: 29 at kernel/workqueue.c:2256 __queue_work+0x2e5/0x1010 kernel/workqueue.c:2254
Modules linked in:
CPU: 1 UID: 0 PID: 29 Comm: ktimers/1 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:__queue_work+0x2e5/0x1010 kernel/workqueue.c:2254
Code: 42 80 3c 28 00 74 08 48 89 ef e8 16 a1 93 00 48 8b 75 00 49 81 c6 68 01 00 00 48 c7 c7 60 ed 09 8b 4c 89 f2 e8 ac 3c f9 ff 90 <0f> 0b 90 90 e9 f2 fe ff ff e8 0d 6a 34 00 eb 2e e8 06 6a 34 00 e9
RSP: 0018:ffffc90000a3f828 EFLAGS: 00010046
RAX: d228e4afda57de00 RBX: 0000000000000000 RCX: ffff88801ca99dc0
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000100
RBP: ffff888028754998 R08: 0000000000000000 R09: 0000000000000100
R10: dffffc0000000000 R11: ffffed1017124863 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88803d644168 R15: ffff88801ca9a8cc
FS: 0000000000000000(0000) GS:ffff8881269c2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31e63fff CR3: 00000000281de000 CR4: 00000000003526f0
Call Trace:
<TASK>
call_timer_fn+0x17b/0x5f0 kernel/time/timer.c:1747
expire_timers kernel/time/timer.c:1793 [inline]
__run_timers kernel/time/timer.c:2372 [inline]
__run_timer_base+0x709/0x970 kernel/time/timer.c:2384
run_timer_base kernel/time/timer.c:2393 [inline]
run_timer_softirq+0xb7/0x180 kernel/time/timer.c:2403
handle_softirqs+0x22c/0x710 kernel/softirq.c:579
__do_softirq kernel/softirq.c:613 [inline]
run_ktimerd+0xcf/0x190 kernel/softirq.c:1043
smpboot_thread_fn+0x542/0xa60 kernel/smpboot.c:160
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x3f9/0x770 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Tested on:
commit: c8bc81a5 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16ccc1f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd9738e00c1bbfb4
dashboard link: https://syzkaller.appspot.com/bug?extid=535bbe83dfc3ae8d4be3
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=17122242580000
Powered by blists - more mailing lists