From: syzbot <syzbot+944c82cd12dd1db5b05f@syzkaller.appspotmail.com>
To: johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] INFO: trying to register non-static key in hci_uart_send_frame (3)
Date: Sun, 31 Oct 2021 22:00:19 -0700 [thread overview]
Message-ID: <000000000000b45deb05cfb30d1c@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 1fc596a56b33 Merge tag 'trace-v5.15-rc6' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b58364b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b160d0631c7a8f26
dashboard link: https://syzkaller.appspot.com/bug?extid=944c82cd12dd1db5b05f
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+944c82cd12dd1db5b05f@syzkaller.appspotmail.com
INFO: trying to register non-static key.
The code is fine but needs lockdep annotation, or maybe
you didn't initialize this object before use?
turning off the locking correctness validator.
CPU: 1 PID: 150 Comm: kworker/u5:0 Not tainted 5.15.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci7 hci_cmd_work
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
assign_lock_key kernel/locking/lockdep.c:939 [inline]
register_lock_class+0xf79/0x10c0 kernel/locking/lockdep.c:1251
__lock_acquire+0x105/0x54a0 kernel/locking/lockdep.c:4894
lock_acquire kernel/locking/lockdep.c:5625 [inline]
lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5590
percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
hci_uart_send_frame+0x8e/0x6c0 drivers/bluetooth/hci_ldisc.c:279
hci_send_frame+0x1c0/0x380 net/bluetooth/hci_core.c:4244
hci_cmd_work+0x202/0x390 net/bluetooth/hci_core.c:5177
process_one_work+0x9bf/0x16b0 kernel/workqueue.c:2297
worker_thread+0x658/0x11f0 kernel/workqueue.c:2444
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Bluetooth: hci6: sending frame failed (-49)
Bluetooth: hci6: sending frame failed (-49)
---
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:[~2021-11-01 5:00 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=000000000000b45deb05cfb30d1c@google.com \
--to=syzbot+944c82cd12dd1db5b05f@syzkaller.appspotmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox