From: syzbot <syzbot+10bd8fe6741eedd2be2e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] BUG: corrupted list in hci_chan_del (2)
Date: Fri, 07 Feb 2025 09:31:03 -0800 [thread overview]
Message-ID: <67a64357.050a0220.f64af.0002.GAE@google.com> (raw)
In-Reply-To: <CABBYNZ+usqU-KkdF=47qLh4u19zu_ao9U3tVXwAJyUZ5OkgmYw@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+10bd8fe6741eedd2be2e@syzkaller.appspotmail.com
Tested-by: syzbot+10bd8fe6741eedd2be2e@syzkaller.appspotmail.com
Tested on:
commit: ed58d103 Add linux-next specific files for 20250207
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12dca1b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=244a34ec1429746
dashboard link: https://syzkaller.appspot.com/bug?extid=10bd8fe6741eedd2be2e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=13538b18580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-02-07 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABBYNZ+usqU-KkdF=47qLh4u19zu_ao9U3tVXwAJyUZ5OkgmYw@mail.gmail.com>
2025-02-07 17:31 ` syzbot [this message]
[not found] <CABBYNZKiusks5ggjr_ZjidreAt=f89zNcpACjEhw-D_zBPUHVg@mail.gmail.com>
2025-02-07 16:40 ` [syzbot] [bluetooth?] BUG: corrupted list in hci_chan_del (2) syzbot
[not found] <20250207122525.2703519-1-lizhi.xu@windriver.com>
2025-02-07 13:00 ` syzbot
[not found] <20250207063721.244699-1-lizhi.xu@windriver.com>
2025-02-07 7:02 ` syzbot
[not found] <20250207040929.2197410-1-lizhi.xu@windriver.com>
2025-02-07 4:43 ` syzbot
[not found] <20250207022033.2444682-1-lizhi.xu@windriver.com>
2025-02-07 2:56 ` syzbot
[not found] <CABBYNZJ2bCo7-g75BZbP8Ch3FUVzLhXe05EonigSThuVyzfhLg@mail.gmail.com>
2025-02-06 22:37 ` syzbot
2025-02-06 13:10 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=67a64357.050a0220.f64af.0002.GAE@google.com \
--to=syzbot+10bd8fe6741eedd2be2e@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.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.