From: syzbot <syzbot+91fd909b6e62ebe06131@syzkaller.appspotmail.com>
To: davem@davemloft.net, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
Date: Wed, 06 Mar 2019 10:04:04 -0800 [thread overview]
Message-ID: <000000000000b7fd51058370d0d9@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: cf08baa29613 Add linux-next specific files for 20190306
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15bc76c7200000
kernel config: https://syzkaller.appspot.com/x/.config?x=c8b6073d992e8217
dashboard link: https://syzkaller.appspot.com/bug?extid=91fd909b6e62ebe06131
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+91fd909b6e62ebe06131@syzkaller.appspotmail.com
BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
turning off the locking correctness validator.
CPU: 0 PID: 11902 Comm: kworker/u5:27 Not tainted 5.0.0-next-20190306 #4
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: hci94 hci_power_on
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
add_chain_cache kernel/locking/lockdep.c:2582 [inline]
lookup_chain_cache_add kernel/locking/lockdep.c:2656 [inline]
validate_chain kernel/locking/lockdep.c:2676 [inline]
__lock_acquire.cold+0x250/0x50d kernel/locking/lockdep.c:3692
lock_acquire+0x16f/0x3f0 kernel/locking/lockdep.c:4202
__flush_work+0x677/0x8a0 kernel/workqueue.c:3034
flush_work+0x18/0x20 kernel/workqueue.c:3060
hci_dev_do_open+0xa92/0x1780 net/bluetooth/hci_core.c:1543
hci_power_on+0x10d/0x580 net/bluetooth/hci_core.c:2173
process_one_work+0x98e/0x1790 kernel/workqueue.c:2269
worker_thread+0x98/0xe40 kernel/workqueue.c:2415
kthread+0x357/0x430 kernel/kthread.c:253
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
next reply other threads:[~2019-03-06 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 18:04 syzbot [this message]
2019-04-11 1:43 ` BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! syzbot
2019-04-11 12:14 ` syzbot
2019-04-11 21:50 ` Benjamin Herrenschmidt
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=000000000000b7fd51058370d0d9@google.com \
--to=syzbot+91fd909b6e62ebe06131@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).