From: syzbot <syzbot+1683f76f1b20b826de67@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (2)
Date: Thu, 02 Nov 2023 22:23:04 -0700 [thread overview]
Message-ID: <000000000000dfd1d2060938b275@google.com> (raw)
In-Reply-To: <20231103051306.721321-1-lizhi.xu@windriver.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
net/bluetooth/sco.c:81:62: error: no member named 'hci_conn' in 'struct sco_conn'
net/bluetooth/sco.c:81:26: error: no member named 'hci_conn' in 'sco_conn'
net/bluetooth/sco.c:81:20: error: initializing 'struct sco_conn *' with an expression of incompatible type 'void'
net/bluetooth/sco.c:82:7: error: no member named 'hci_conn' in 'struct sco_conn'
Tested on:
commit: 8de1e7af Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=3e6feaeda5dcbc27
dashboard link: https://syzkaller.appspot.com/bug?extid=1683f76f1b20b826de67
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=15ec2687680000
next parent reply other threads:[~2023-11-03 5:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231103051306.721321-1-lizhi.xu@windriver.com>
2023-11-03 5:23 ` syzbot [this message]
[not found] <20231104054009.3030149-1-lizhi.xu@windriver.com>
2023-11-04 6:00 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (2) syzbot
[not found] <20231104044729.2716748-1-lizhi.xu@windriver.com>
2023-11-04 5:17 ` syzbot
[not found] <20231104032323.2233372-1-lizhi.xu@windriver.com>
2023-11-04 3:36 ` syzbot
[not found] <20231103121804.1421-1-hdanton@sina.com>
2023-11-03 12:43 ` syzbot
[not found] <20231103080016.3516726-1-lizhi.xu@windriver.com>
2023-11-03 8:17 ` syzbot
[not found] <20231103070111.2610655-1-lizhi.xu@windriver.com>
2023-11-03 7:11 ` syzbot
[not found] <20231103010143.3182694-1-lizhi.xu@windriver.com>
2023-11-03 3:54 ` syzbot
2023-11-02 22:01 syzbot
2024-02-17 2:09 ` syzbot
2024-02-17 10:57 ` Hillf Danton
2024-02-17 11:23 ` syzbot
2024-02-18 8:44 ` Hillf Danton
2024-02-18 8:46 ` syzbot
2024-02-17 19:33 ` syzbot
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=000000000000dfd1d2060938b275@google.com \
--to=syzbot+1683f76f1b20b826de67@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--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.