BUG: corrupted list in kobject_add_internal (2)

14 views
Skip to first unread message

syzbot

unread,
Jan 14, 2021, 11:40:23 AMJan 14
to gre...@linuxfoundation.org, linux-...@vger.kernel.org, raf...@kernel.org, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2ff90100 Merge tag 'hwmon-for-v5.11-rc3' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12cee4cf500000
kernel config: https://syzkaller.appspot.com/x/.config?x=7c84b50cb7dc0e2f
dashboard link: https://syzkaller.appspot.com/bug?extid=77966d28c046cef546cb
compiler: gcc (GCC) 10.1.0-syz 20200507

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+77966d...@syzkaller.appspotmail.com

list_add double add: new=ffff888073202420, prev=ffff888073202420, next=ffff88814077de00.
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:29!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8482 Comm: kworker/u5:1 Not tainted 5.11.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci4 hci_rx_work
RIP: 0010:__list_add_valid.cold+0x26/0x3c lib/list_debug.c:29
Code: 77 cf fb fa 4c 89 e1 48 c7 c7 e0 7f 9e 89 e8 36 34 f3 ff 0f 0b 48 89 f2 4c 89 e1 48 89 ee 48 c7 c7 20 81 9e 89 e8 1f 34 f3 ff <0f> 0b 48 89 f1 48 c7 c7 a0 80 9e 89 4c 89 e6 e8 0b 34 f3 ff 0f 0b
RSP: 0018:ffffc90001b97830 EFLAGS: 00010282
RAX: 0000000000000058 RBX: ffff88814077de00 RCX: 0000000000000000
RDX: ffff88806db94240 RSI: ffffffff815b6a45 RDI: fffff52000372ef8
RBP: ffff888073202420 R08: 0000000000000058 R09: 0000000000000000
R10: ffffffff815afbee R11: 0000000000000000 R12: ffff88814077de00
R13: ffff8880a0181298 R14: ffff888073202438 R15: ffff888073202420
FS: 0000000000000000(0000) GS:ffff8880b9f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000016b9e60 CR3: 000000007a823000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
__list_add include/linux/list.h:67 [inline]
list_add_tail include/linux/list.h:100 [inline]
kobj_kset_join lib/kobject.c:196 [inline]
kobject_add_internal+0x18d/0xa60 lib/kobject.c:246
kobject_add_varg lib/kobject.c:390 [inline]
kobject_add+0x150/0x1c0 lib/kobject.c:442
device_add+0x36a/0x1d90 drivers/base/core.c:3024
hci_conn_add_sysfs+0x97/0x1a0 net/bluetooth/hci_sysfs.c:53
hci_conn_complete_evt net/bluetooth/hci_event.c:2643 [inline]
hci_event_packet+0x9e3/0x7d60 net/bluetooth/hci_event.c:6153
hci_rx_work+0x511/0xd30 net/bluetooth/hci_core.c:4971
process_one_work+0x98d/0x15f0 kernel/workqueue.c:2275
worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
Modules linked in:
---[ end trace f938414eaac88f6e ]---
RIP: 0010:__list_add_valid.cold+0x26/0x3c lib/list_debug.c:29
Code: 77 cf fb fa 4c 89 e1 48 c7 c7 e0 7f 9e 89 e8 36 34 f3 ff 0f 0b 48 89 f2 4c 89 e1 48 89 ee 48 c7 c7 20 81 9e 89 e8 1f 34 f3 ff <0f> 0b 48 89 f1 48 c7 c7 a0 80 9e 89 4c 89 e6 e8 0b 34 f3 ff 0f 0b
RSP: 0018:ffffc90001b97830 EFLAGS: 00010282
RAX: 0000000000000058 RBX: ffff88814077de00 RCX: 0000000000000000
RDX: ffff88806db94240 RSI: ffffffff815b6a45 RDI: fffff52000372ef8
RBP: ffff888073202420 R08: 0000000000000058 R09: 0000000000000000
R10: ffffffff815afbee R11: 0000000000000000 R12: ffff88814077de00
R13: ffff8880a0181298 R14: ffff888073202438 R15: ffff888073202420
FS: 0000000000000000(0000) GS:ffff8880b9f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000016b9e60 CR3: 000000000b08e000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600


---
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

unread,
May 10, 2021, 12:34:15 PMMay 10
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages