From: syzbot <syzbot+e07ad07cb2283bc5bf57@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 kref_put
Date: Sat, 17 Sep 2022 23:13:35 -0700 [thread overview]
Message-ID: <000000000000c0ee8705e8ed7e7e@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a6b443748715 Merge branch 'for-next/core', remote-tracking..
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=104c56a0880000
kernel config: https://syzkaller.appspot.com/x/.config?x=14bf9ec0df433b27
dashboard link: https://syzkaller.appspot.com/bug?extid=e07ad07cb2283bc5bf57
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
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/81b491dd5861/disk-a6b44374.raw.xz
vmlinux: https://storage.googleapis.com/69c979cdc99a/vmlinux-a6b44374.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e07ad07cb2283bc5bf57@syzkaller.appspotmail.com
list_del corruption. prev->next should be ffff0000c953d4c8, but was 0000000000000000. (prev=ffff0000fc3536c8)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:61!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 44 Comm: kworker/u5:0 Not tainted 6.0.0-rc4-syzkaller-17255-ga6b443748715 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Workqueue: hci5 hci_error_reset
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 : ffff80000f683b10
x29: ffff80000f683b10 x28: ffff80000d2bb000 x27: ffff0000c6e49c25
x26: 0000000000000000 x25: 0000000000000000 x24: ffff0000c0dec980
x23: ffff0000c0d93500 x22: ffff800009a56428 x21: ffff0000c0f30149
x20: ffff0000c953d4c0 x19: ffff0000c953d4d8 x18: 00000000000000c0
x17: 20747562202c3863 x16: ffff80000db78658 x15: ffff0000c0d93500
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c0d93500
x11: ff808000081c1fa0 x10: 0000000000000000 x9 : 74f127b5afecc300
x8 : 74f127b5afecc300 x7 : ffff8000081965e0 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff0001fefddcd0 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 include/linux/list.h:148 [inline]
klist_release lib/klist.c:189 [inline]
kref_put+0x6c/0x1d0 include/linux/kref.h:65
klist_dec_and_del lib/klist.c:206 [inline]
klist_put lib/klist.c:217 [inline]
klist_del+0x58/0xb0 lib/klist.c:230
device_del+0x280/0x5bc drivers/base/core.c:3699
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_conn_hash_flush+0xe8/0x148 net/bluetooth/hci_conn.c:2367
hci_dev_close_sync+0x48c/0x9e0 net/bluetooth/hci_sync.c:4476
hci_dev_do_close net/bluetooth/hci_core.c:554 [inline]
hci_error_reset+0xac/0x154 net/bluetooth/hci_core.c:1050
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
Code: d001b4a0 91365000 aa0803e3 94a7897a (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 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-18 6:13 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=000000000000c0ee8705e8ed7e7e@google.com \
--to=syzbot+e07ad07cb2283bc5bf57@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.