Message-ID: <000000000000224117061db5a39c@google.com>
Date: Sat, 20 Jul 2024 15:50:23 -0700
From: syzbot <syzbot+f32bdeda1c9146004da8@...kaller.appspotmail.com>
To: johan.hedberg@...il.com, linux-bluetooth@...r.kernel.org, 
	linux-kernel@...r.kernel.org, luiz.dentz@...il.com, marcel@...tmann.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [bluetooth?] WARNING in hci_send_acl (3)

Hello,

syzbot found the following issue on:

HEAD commit:    c912bf709078 Merge remote-tracking branches 'origin/arm64-..
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=171be3a5980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=79a49b0b9ffd6585
dashboard link: https://syzkaller.appspot.com/bug?extid=f32bdeda1c9146004da8
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fea69a9d153c/disk-c912bf70.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/be06762a72ef/vmlinux-c912bf70.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6c8e58b4215d/Image-c912bf70.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 7434 at kernel/workqueue.c:2282 current_wq_worker kernel/workqueue_internal.h:69 [inline]
WARNING: CPU: 1 PID: 7434 at kernel/workqueue.c:2282 is_chained_work kernel/workqueue.c:2224 [inline]
WARNING: CPU: 1 PID: 7434 at kernel/workqueue.c:2282 __queue_work+0xe0c/0x12ac kernel/workqueue.c:2281
Modules linked in:
CPU: 1 PID: 7434 Comm: syz.2.363 Not tainted 6.10.0-rc7-syzkaller-gc912bf709078 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __queue_work+0xe0c/0x12ac kernel/workqueue_internal.h:69
lr : current_wq_worker kernel/workqueue_internal.h:69 [inline]
lr : is_chained_work kernel/workqueue.c:2224 [inline]
lr : __queue_work+0xe0c/0x12ac kernel/workqueue.c:2281
sp : ffff8000a0aa7240
x29: ffff8000a0aa7290 x28: 1fffe000196d0e41 x27: 0000000000000004
x26: dfff800000000000 x25: ffff0000d17ae800 x24: 0000000000000008
x23: 1fffe0001af1e3c9 x22: ffff0000d17ae9c0 x21: 0000000000400140
x20: ffff0000d78f1e40 x19: ffff0000d8678b18 x18: ffff8000a0aa72e0
x17: ffff80008f0fd000 x16: ffff800082f8f174 x15: 0000000000000001
x14: 1fffe0001b0cf163 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000040000 x10: 000000000003ffff x9 : ffff8000a1f1f000
x8 : 0000000000040000 x7 : ffff800089145000 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : ffff80008022dbe8
x2 : ffff0000d8678b18 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
 current_wq_worker kernel/workqueue_internal.h:69 [inline]
 is_chained_work kernel/workqueue.c:2224 [inline]
 __queue_work+0xe0c/0x12ac kernel/workqueue.c:2281
 queue_work_on+0xe0/0x1a0 kernel/workqueue.c:2411
 queue_work include/linux/workqueue.h:621 [inline]
 hci_send_acl+0x768/0xa50 net/bluetooth/hci_core.c:3250
 l2cap_do_send+0x188/0x288 net/bluetooth/l2cap_core.c:996
 l2cap_chan_send+0x13dc/0x211c net/bluetooth/l2cap_core.c:2577
 l2cap_sock_sendmsg+0x184/0x2a8 net/bluetooth/l2cap_sock.c:1128
 sock_sendmsg_nosec net/socket.c:730 [inline]
 __sock_sendmsg net/socket.c:745 [inline]
 ____sys_sendmsg+0x4d8/0x77c net/socket.c:2585
 ___sys_sendmsg net/socket.c:2639 [inline]
 __sys_sendmmsg+0x30c/0x6b0 net/socket.c:2725
 __do_sys_sendmmsg net/socket.c:2754 [inline]
 __se_sys_sendmmsg net/socket.c:2751 [inline]
 __arm64_sys_sendmmsg+0xa0/0xbc net/socket.c:2751
 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:131
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:150
 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712
 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730
 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598
irq event stamp: 13644
hardirqs last  enabled at (13643): [<ffff80008afc3e68>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:85 [inline]
hardirqs last  enabled at (13643): [<ffff80008afc3e68>] exit_to_kernel_mode+0xdc/0x10c arch/arm64/kernel/entry-common.c:95
hardirqs last disabled at (13644): [<ffff80008022dbd4>] queue_work_on+0x50/0x1a0 kernel/workqueue.c:2407
softirqs last  enabled at (13586): [<ffff800089111350>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last  enabled at (13586): [<ffff800089111350>] release_sock+0x154/0x1b8 net/core/sock.c:3558
softirqs last disabled at (13584): [<ffff800089111238>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (13584): [<ffff800089111238>] release_sock+0x3c/0x1b8 net/core/sock.c:3547
---[ end trace 0000000000000000 ]---


---
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 syzkaller@...glegroups.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

Powered by blists - more mailing lists