From: syzbot <syzbot+5067576ebe3f37f2cca4@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [bluetooth?] WARNING: bad unlock balance in l2cap_bredr_sig_cmd
Date: Sun, 16 Apr 2023 22:35:40 -0700 [thread overview]
Message-ID: <000000000000adcd3c05f9818f7f@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7a934f4bd7d6 Merge tag 'riscv-for-linus-6.3-rc7' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17444c3fc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=759d5e665e47a55
dashboard link: https://syzkaller.appspot.com/bug?extid=5067576ebe3f37f2cca4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df89fd1d6599/disk-7a934f4b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e76edf369cbd/vmlinux-7a934f4b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23ad78b092d3/bzImage-7a934f4b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5067576ebe3f37f2cca4@syzkaller.appspotmail.com
=====================================
WARNING: bad unlock balance detected!
6.3.0-rc6-syzkaller-00173-g7a934f4bd7d6 #0 Not tainted
-------------------------------------
kworker/u5:0/19118 is trying to release lock (&conn->chan_lock) at:
[<ffffffff89aea4c5>] l2cap_bredr_sig_cmd+0x875/0x9cb0 net/bluetooth/l2cap_core.c:5748
but there are no more locks to release!
other info that might help us debug this:
2 locks held by kworker/u5:0/19118:
#0: ffff88804175e938 ((wq_completion)hci2#2){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2363
#1: ffffc90005077d20 ((work_completion)(&hdev->rx_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2365
stack backtrace:
CPU: 0 PID: 19118 Comm: kworker/u5:0 Not tainted 6.3.0-rc6-syzkaller-00173-g7a934f4bd7d6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Workqueue: hci2 hci_rx_work
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
print_unlock_imbalance_bug+0x252/0x2c0 kernel/locking/lockdep.c:5109
__lock_release kernel/locking/lockdep.c:5346 [inline]
lock_release+0x59d/0x9d0 kernel/locking/lockdep.c:5689
__mutex_unlock_slowpath+0xe2/0x750 kernel/locking/mutex.c:907
l2cap_bredr_sig_cmd+0x875/0x9cb0 net/bluetooth/l2cap_core.c:5748
l2cap_sig_channel net/bluetooth/l2cap_core.c:6507 [inline]
l2cap_recv_frame+0xa5a/0x8990 net/bluetooth/l2cap_core.c:7786
hci_acldata_packet net/bluetooth/hci_core.c:3828 [inline]
hci_rx_work+0x58e/0xa90 net/bluetooth/hci_core.c:4063
process_one_work+0x8a0/0x10e0 kernel/workqueue.c:2390
worker_thread+0xa63/0x1210 kernel/workqueue.c:2537
kthread+0x270/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Bluetooth: hci2: ACL packet for unknown connection handle 173
Bluetooth: hci2: ACL packet for unknown connection handle 173
Bluetooth: Unexpected start frame (len 16)
Bluetooth: Unexpected start frame (len 16)
Bluetooth: Unexpected start frame (len 16)
Bluetooth: hci4: Received unexpected HCI Event 0x00
Bluetooth: hci4: Received unexpected HCI Event 0x00
Bluetooth: hci4: Received unexpected HCI Event 0x00
Bluetooth: Unexpected start frame (len 20)
Bluetooth: Unexpected start frame (len 20)
Bluetooth: Unexpected start frame (len 28)
Bluetooth: hci1: Malformed Event: 0x02
Bluetooth: Unexpected start frame (len 28)
Bluetooth: Unexpected start frame (len 28)
Bluetooth: Unexpected start frame (len 28)
Bluetooth: Unexpected start frame (len 28)
Bluetooth: hci2: command 0x0419 tx timeout
Bluetooth: hci4: ACL packet for unknown connection handle 3017
Bluetooth: hci4: ACL packet for unknown connection handle 3017
Bluetooth: hci4: ACL packet for unknown connection handle 3017
Bluetooth: hci4: ACL packet for unknown connection handle 2303
Bluetooth: hci5: ACL packet for unknown connection handle 0
Bluetooth: Frame is too long (len 78, expected len 4)
Bluetooth: Frame is too long (len 78, expected len 4)
Bluetooth: Frame is too long (len 78, expected len 4)
Bluetooth: Frame is too long (len 78, expected len 4)
Bluetooth: hci5: ACL packet for unknown connection handle 233
Bluetooth: hci5: ACL packet for unknown connection handle 233
Bluetooth: hci5: ACL packet for unknown connection handle 233
Bluetooth: Unexpected continuation frame (len 28)
Bluetooth: Unexpected continuation frame (len 28)
Bluetooth: Unexpected start frame (len 16)
Bluetooth: Unexpected start frame (len 16)
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci1: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci2: ACL packet for unknown connection handle 2048
Bluetooth: hci0: command 0x0406 tx timeout
---
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@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2023-04-17 5:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000adcd3c05f9818f7f@google.com \
--to=syzbot+5067576ebe3f37f2cca4@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.