public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f098d64cc684b8dbaf65@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] [usb?] memory leak in __hci_cmd_sync_sk
Date: Sun, 23 Nov 2025 07:23:02 -0800	[thread overview]
Message-ID: <692326d6.a70a0220.d98e3.0067.GAE@google.com> (raw)
In-Reply-To: <tencent_274B18740376CF66763CD3366C9684367209@qq.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+f098d64cc684b8dbaf65@syzkaller.appspotmail.com
Tested-by: syzbot+f098d64cc684b8dbaf65@syzkaller.appspotmail.com

Tested on:

commit:         d13f3ac6 Merge tag 'mips-fixes_6.18_1' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=168cd8b4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f30cc590c4f6da44
dashboard link: https://syzkaller.appspot.com/bug?extid=f098d64cc684b8dbaf65
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11a6b97c580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2025-11-23 15:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 14:24 [syzbot] [bluetooth?] [usb?] memory leak in __hci_cmd_sync_sk syzbot
2025-11-18  2:53 ` Edward Adam Davis
2025-11-18  3:24   ` syzbot
2025-11-18  3:40 ` Edward Adam Davis
2025-11-18  3:54   ` syzbot
2025-11-18  3:56 ` Edward Adam Davis
2025-11-18  4:24   ` syzbot
2025-11-19  2:46 ` shaurya
2025-11-19  3:22 ` Edward Adam Davis
2025-11-19  3:47   ` syzbot
2025-11-19 18:45 ` shaurya
2025-11-19 19:32   ` syzbot
2025-11-20 13:27 ` Edward Adam Davis
2025-11-20 13:59   ` syzbot
2025-11-20 14:11 ` Edward Adam Davis
2025-11-20 14:45   ` syzbot
2025-11-20 14:54 ` Edward Adam Davis
2025-11-20 15:27   ` syzbot
2025-11-21  0:05 ` Edward Adam Davis
2025-11-21  0:34   ` syzbot
2025-11-21  0:55 ` Edward Adam Davis
2025-11-21  2:14   ` syzbot
2025-11-21  0:57 ` Edward Adam Davis
2025-11-21  2:32   ` syzbot
2025-11-21  6:17 ` Edward Adam Davis
2025-11-21  8:08   ` syzbot
2025-11-21  9:06 ` Edward Adam Davis
2025-11-21 14:36   ` syzbot
2025-11-22  7:09 ` Edward Adam Davis
2025-11-22 10:23   ` syzbot
2025-11-22 14:14 ` Edward Adam Davis
2025-11-22 14:39   ` syzbot
2025-11-23 14:05 ` Edward Adam Davis
2025-11-23 15:23   ` syzbot [this message]
2025-11-23 14:33 ` Edward Adam Davis
2025-11-23 16:09   ` syzbot
2025-11-23 15:08 ` Edward Adam Davis
2025-11-23 16:30   ` 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=692326d6.a70a0220.d98e3.0067.GAE@google.com \
    --to=syzbot+f098d64cc684b8dbaf65@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox