From: syzbot <syzbot+1683f76f1b20b826de67@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (2)
Date: Sun, 18 Feb 2024 00:46:04 -0800 [thread overview]
Message-ID: <000000000000dfd6170611a40107@google.com> (raw)
In-Reply-To: <20240218084414.1254-1-hdanton@sina.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git on commit 2c3b09aac00d: failed to run ["git" "fetch" "--force" "--tags" "fc608f7504e8b3e110eb6e7b798cef357818c5e1" "2c3b09aac00d"]: exit status 128
fatal: couldn't find remote ref 2c3b09aac00d
Tested on:
commit: [unknown
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 2c3b09aac00d
kernel config: https://syzkaller.appspot.com/x/.config?x=176d2dcbf8ba7017
dashboard link: https://syzkaller.appspot.com/bug?extid=1683f76f1b20b826de67
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=1219de58180000
next prev parent reply other threads:[~2024-02-18 8:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 22:01 [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (2) syzbot
2023-11-03 1:01 ` [syzbot] test uaf in hci_conn_drop syzbot
2023-11-03 5:13 ` syzbot
2023-11-03 7:01 ` syzbot
2023-11-03 8:00 ` syzbot
2023-11-04 3:23 ` syzbot
2023-11-04 4:47 ` syzbot
2023-11-04 5:40 ` syzbot
2024-02-17 2:09 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (2) 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 [this message]
2024-02-17 19:33 ` syzbot
[not found] <20231103010143.3182694-1-lizhi.xu@windriver.com>
2023-11-03 3:54 ` syzbot
[not found] <20231103051306.721321-1-lizhi.xu@windriver.com>
2023-11-03 5:23 ` syzbot
[not found] <20231103070111.2610655-1-lizhi.xu@windriver.com>
2023-11-03 7:11 ` syzbot
[not found] <20231103080016.3516726-1-lizhi.xu@windriver.com>
2023-11-03 8:17 ` syzbot
[not found] <20231103121804.1421-1-hdanton@sina.com>
2023-11-03 12:43 ` syzbot
[not found] <20231104032323.2233372-1-lizhi.xu@windriver.com>
2023-11-04 3:36 ` syzbot
[not found] <20231104044729.2716748-1-lizhi.xu@windriver.com>
2023-11-04 5:17 ` syzbot
[not found] <20231104054009.3030149-1-lizhi.xu@windriver.com>
2023-11-04 6:00 ` 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=000000000000dfd6170611a40107@google.com \
--to=syzbot+1683f76f1b20b826de67@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.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.