From: syzbot <syzbot+830d9e3fa61968246abd@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] general protection fault in btintel_read_version
Date: Wed, 17 Jan 2024 17:56:04 -0800 [thread overview]
Message-ID: <0000000000008d8f1f060f2eaadc@google.com> (raw)
In-Reply-To: <tencent_7ED368C373A96E43A20445F772B77FC6CF05@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+830d9e3fa61968246abd@syzkaller.appspotmail.com
Tested on:
commit: 943b9f0a Add linux-next specific files for 20240117
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=10fab583e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=12af1d067b6a6d19
dashboard link: https://syzkaller.appspot.com/bug?extid=830d9e3fa61968246abd
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=132f7913e80000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-01-18 1:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 12:05 [syzbot] [bluetooth?] general protection fault in btintel_read_version syzbot
2024-01-17 13:37 ` Edward Adam Davis
2024-01-17 15:45 ` syzbot
2024-01-17 22:53 ` Edward Adam Davis
2024-01-18 1:56 ` syzbot [this message]
2024-01-18 4:40 ` [PATCH next] bluetooth/btintel: fix null ptr deref " Edward Adam Davis
2024-01-18 5:32 ` [next] " bluez.test.bot
2024-01-25 20:50 ` [PATCH next] " patchwork-bot+bluetooth
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=0000000000008d8f1f060f2eaadc@google.com \
--to=syzbot+830d9e3fa61968246abd@syzkaller.appspotmail.com \
--cc=eadavis@qq.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.