From: syzbot <syzbot+e32111a3390bdf27b0c9@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] BUG: corrupted list in hci_register_dev
Date: Mon, 05 Sep 2022 02:20:27 -0700 [thread overview]
Message-ID: <0000000000001bd49d05e7ea9773@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: b27a3ca08ba7 Add linux-next specific files for 20220829
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15a9cf13080000
kernel config: https://syzkaller.appspot.com/x/.config?x=e2eb01587c47db4c
dashboard link: https://syzkaller.appspot.com/bug?extid=e32111a3390bdf27b0c9
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+e32111a3390bdf27b0c9@syzkaller.appspotmail.com
list_add corruption. prev->next should be next (ffff888145f20188), but was ffff88807c3000c8. (prev=ffff88807cf2d8c8).
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:30!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 18538 Comm: kworker/1:19 Not tainted 6.0.0-rc3-next-20220829-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Workqueue: events vhci_open_timeout
RIP: 0010:__list_add_valid.cold+0x56/0x58 lib/list_debug.c:30
Code: 0b 48 89 f2 4c 89 e1 48 89 ee 48 c7 c7 00 31 49 8a e8 76 d5 f0 ff 0f 0b 48 89 f1 48 c7 c7 80 30 49 8a 4c 89 e6 e8 62 d5 f0 ff <0f> 0b 4c 89 e1 48 89 ee 48 c7 c7 e0 32 49 8a e8 4e d5 f0 ff 0f 0b
RSP: 0018:ffffc90005ed7af0 EFLAGS: 00010282
RAX: 0000000000000075 RBX: ffff88806558fcc0 RCX: 0000000000000000
RDX: ffff88807e7a8000 RSI: ffffffff816204f8 RDI: fffff52000bdaf50
RBP: ffff88806558fcc8 R08: 0000000000000075 R09: 0000000000000000
R10: 0000000000000001 R11: 6464615f7473696c R12: ffff888145f20188
R13: ffff88807cf2d8c8 R14: ffff888145f20190 R15: ffff888145f20188
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffcdeb19cd0 CR3: 000000000bc8e000 CR4: 00000000003526e0
Call Trace:
<TASK>
__list_add include/linux/list.h:69 [inline]
list_add_tail include/linux/list.h:102 [inline]
add_tail lib/klist.c:104 [inline]
klist_add_tail+0x158/0x2a0 lib/klist.c:137
device_add+0xda7/0x1e90 drivers/base/core.c:3534
hci_register_dev+0x2f6/0xbb0 net/bluetooth/hci_core.c:2593
__vhci_create_device+0x393/0x7d0 drivers/bluetooth/hci_vhci.c:336
vhci_create_device drivers/bluetooth/hci_vhci.c:374 [inline]
vhci_open_timeout+0x38/0x50 drivers/bluetooth/hci_vhci.c:531
process_one_work+0x991/0x1610 kernel/workqueue.c:2289
worker_thread+0x665/0x1080 kernel/workqueue.c:2436
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_add_valid.cold+0x56/0x58 lib/list_debug.c:30
Code: 0b 48 89 f2 4c 89 e1 48 89 ee 48 c7 c7 00 31 49 8a e8 76 d5 f0 ff 0f 0b 48 89 f1 48 c7 c7 80 30 49 8a 4c 89 e6 e8 62 d5 f0 ff <0f> 0b 4c 89 e1 48 89 ee 48 c7 c7 e0 32 49 8a e8 4e d5 f0 ff 0f 0b
RSP: 0018:ffffc90005ed7af0 EFLAGS: 00010282
RAX: 0000000000000075 RBX: ffff88806558fcc0 RCX: 0000000000000000
RDX: ffff88807e7a8000 RSI: ffffffff816204f8 RDI: fffff52000bdaf50
RBP: ffff88806558fcc8 R08: 0000000000000075 R09: 0000000000000000
R10: 0000000000000001 R11: 6464615f7473696c R12: ffff888145f20188
R13: ffff88807cf2d8c8 R14: ffff888145f20190 R15: ffff888145f20188
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffcdeb19cd0 CR3: 000000000bc8e000 CR4: 00000000003526e0
---
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:[~2022-09-05 9:20 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=0000000000001bd49d05e7ea9773@google.com \
--to=syzbot+e32111a3390bdf27b0c9@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 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.