BUG: corrupted list in kobject_add_internal (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11a5cc50880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=d96ee9f9c779aea31787
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

list_add double add: new=ffff8880a4e71198, prev=ffff8880a4e71198, next=ffff8880b5b18800.
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:29!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8129 Comm: kworker/u5:1 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Workqueue: hci2 hci_rx_work
RIP: 0010:__list_add_valid.cold+0x26/0x3c lib/list_debug.c:29
Code: 7c 3f 7a fb 4c 89 e1 48 c7 c7 e0 e1 b3 88 e8 3c 43 f7 ff 0f 0b 48 89 f2 4c 89 e1 48 89 ee 48 c7 c7 20 e3 b3 88 e8 25 43 f7 ff <0f> 0b 48 89 f1 48 c7 c7 a0 e2 b3 88 4c 89 e6 e8 11 43 f7 ff 0f 0b
RSP: 0000:ffff88809f187868 EFLAGS: 00010286
RAX: 0000000000000058 RBX: ffff8880b5b18800 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1013e30eff
RBP: ffff8880a4e71198 R08: 0000000000000058 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880b5b18800
R13: ffff88809e7b12d0 R14: ffff8880a4e711b0 R15: ffff8880a4e71198
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7fd95091b8 CR3: 00000000b4803000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_add include/linux/list.h:60 [inline]
list_add_tail include/linux/list.h:93 [inline]
kobj_kset_join lib/kobject.c:188 [inline]
kobject_add_internal+0x18d/0x9c0 lib/kobject.c:238
kobject_add_varg lib/kobject.c:382 [inline]
kobject_add+0x150/0x1c0 lib/kobject.c:426
device_add+0x37b/0x16d0 drivers/base/core.c:2122
hci_conn_add_sysfs+0x97/0x1a0 net/bluetooth/hci_sysfs.c:53
hci_conn_complete_evt net/bluetooth/hci_event.c:2445 [inline]
hci_event_packet+0x2647/0x7e20 net/bluetooth/hci_event.c:5825
hci_rx_work+0x4ad/0xc70 net/bluetooth/hci_core.c:4380
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace a8d9612a0cbc29bf ]---
RIP: 0010:__list_add_valid.cold+0x26/0x3c lib/list_debug.c:29
Code: 7c 3f 7a fb 4c 89 e1 48 c7 c7 e0 e1 b3 88 e8 3c 43 f7 ff 0f 0b 48 89 f2 4c 89 e1 48 89 ee 48 c7 c7 20 e3 b3 88 e8 25 43 f7 ff <0f> 0b 48 89 f1 48 c7 c7 a0 e2 b3 88 4c 89 e6 e8 11 43 f7 ff 0f 0b
RSP: 0000:ffff88809f187868 EFLAGS: 00010286
RAX: 0000000000000058 RBX: ffff8880b5b18800 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1013e30eff
RBP: ffff8880a4e71198 R08: 0000000000000058 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880b5b18800
R13: ffff88809e7b12d0 R14: ffff8880a4e711b0 R15: ffff8880a4e71198
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7fd95091b8 CR3: 00000000b4803000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.