[syzbot] BUG: corrupted list in hci_conn_del_sysfs

14 views
Skip to first unread message

syzbot

unread,
Oct 15, 2022, 8:15:52 PM10/15/22
to gre...@linuxfoundation.org, linux-...@vger.kernel.org, raf...@kernel.org, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: bbed346d5a96 Merge branch 'for-next/core' into for-kernelci
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=118a79aa880000
kernel config: https://syzkaller.appspot.com/x/.config?x=3a4a45d2d827c1e
dashboard link: https://syzkaller.appspot.com/bug?extid=1c67b5b16a787760811b
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13721f62880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127b44c2880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e8e91bc79312/disk-bbed346d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c1cb3fb3b77e/vmlinux-bbed346d.xz

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

Bluetooth: hci0: failed to register connection device
list_del corruption. prev->next should be ffff0000c7b86540, but was ffff0000c923f540. (prev=ffff0000c923f540)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:61!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 3033 Comm: kworker/u5:2 Not tainted 6.0.0-rc7-syzkaller-18095-gbbed346d5a96 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
Workqueue: hci0 hci_rx_work
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __list_del_entry_valid+0xbc/0xd0 lib/list_debug.c:59
lr : __list_del_entry_valid+0xbc/0xd0 lib/list_debug.c:59
sp : ffff80001273baa0
x29: ffff80001273baa0 x28: ffff80000c5286b0 x27: ffff0000c903c100
x26: ffff0000c7b86648 x25: ffff0000c7b86658 x24: 0000000000000000
x23: ffff0000c37c3500 x22: 0000000004208060 x21: 000000000000000c
x20: ffff0000c7b86540 x19: ffff0000c7b86538 x18: 00000000000000c0
x17: 20747562202c3034 x16: ffff80000db49158 x15: ffff0000c37c3500
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c37c3500
x11: ff808000081c0d5c x10: 0000000000000000 x9 : 0333914f3ceeb000
x8 : 0333914f3ceeb000 x7 : ffff80000819545c x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff0001fefbecd0 x1 : 0000000100000001 x0 : 000000000000006d
Call trace:
__list_del_entry_valid+0xbc/0xd0 lib/list_debug.c:59
__list_del_entry include/linux/list.h:134 [inline]
list_del_init include/linux/list.h:206 [inline]
kobj_kset_leave lib/kobject.c:175 [inline]
__kobject_del+0xa8/0x1f8 lib/kobject.c:592
kobject_del+0x28/0x110 lib/kobject.c:611
device_del+0x46c/0x5bc drivers/base/core.c:3715
hci_conn_del_sysfs+0xb0/0xfc net/bluetooth/hci_sysfs.c:78
hci_conn_cleanup+0x2d4/0x380 net/bluetooth/hci_conn.c:147
hci_conn_del+0x144/0x2a8 net/bluetooth/hci_conn.c:1022
hci_le_cis_estabilished_evt+0x1c4/0x21c net/bluetooth/hci_event.c:6805
hci_le_meta_evt+0x1e4/0x230 net/bluetooth/hci_event.c:7110
hci_event_func net/bluetooth/hci_event.c:7440 [inline]
hci_event_packet+0x4e0/0x60c net/bluetooth/hci_event.c:7495
hci_rx_work+0x1a4/0x2f4 net/bluetooth/hci_core.c:4007
process_one_work+0x2d8/0x504 kernel/workqueue.c:2289
worker_thread+0x340/0x610 kernel/workqueue.c:2436
kthread+0x12c/0x158 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
Code: d001b460 91346000 aa0803e3 94a76157 (d4210000)
---[ 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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

syzbot

unread,
Feb 24, 2023, 12:48:37 PM2/24/23
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages