All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9aa47cd4633a3cf92a80@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_pending_remove
Date: Sun, 16 Nov 2025 00:54:02 -0800	[thread overview]
Message-ID: <6919912a.a70a0220.3124cb.0077.GAE@google.com> (raw)
In-Reply-To: <tencent_2E03CFCC0DBB25D10DB89200DD9E5DD71907@qq.com>

Hello,

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

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

Tested on:

commit:         c9dfb92d Merge branch 'mlx5-next' of git://git.kernel...
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1629a212580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4dda49799a90cd0f
dashboard link: https://syzkaller.appspot.com/bug?extid=9aa47cd4633a3cf92a80
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1234dd32580000

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

  reply	other threads:[~2025-11-16  8:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16  6:34 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_pending_remove syzbot
2025-11-16  8:02 ` Edward Adam Davis
2025-11-16  8:21   ` syzbot
2025-11-16  8:29 ` Edward Adam Davis
2025-11-16  8:54   ` syzbot [this message]
2025-11-16  9:04 ` [PATCH] Bluetooth: hci_sock: Prevent race in socket write iter and sock bind Edward Adam Davis
2025-11-16  9:35   ` bluez.test.bot
2025-11-19 14:30   ` [PATCH] " 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=6919912a.a70a0220.3124cb.0077.GAE@google.com \
    --to=syzbot+9aa47cd4633a3cf92a80@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.