From: patchwork-bot+bluetooth@kernel.org
To: Edward Adam Davis <eadavis@qq.com>
Cc: syzbot+489f78df4709ac2bfdd3@syzkaller.appspotmail.com,
johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] Bluetooth: SCO: remove the redundant sco_conn_put
Date: Tue, 26 Nov 2024 16:10:30 +0000 [thread overview]
Message-ID: <173263743076.458202.14094125770586556197.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_10C852E0467D89872ECD2EFCCC9C27D68606@qq.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 26 Nov 2024 07:58:43 +0800 you wrote:
> When adding conn, it is necessary to increase and retain the conn reference
> count at the same time.
>
> Another problem was fixed along the way, conn_put is missing when hcon is NULL
> in the timeout routine.
>
> Fixes: e6720779ae61 ("Bluetooth: SCO: Use kref to track lifetime of sco_conn")
> Reported-and-tested-by: syzbot+489f78df4709ac2bfdd3@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=489f78df4709ac2bfdd3
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
>
> [...]
Here is the summary with links:
- Bluetooth: SCO: remove the redundant sco_conn_put
https://git.kernel.org/bluetooth/bluetooth-next/c/ad0d88dc33bb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-26 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 13:16 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in sco_sock_connect syzbot
2024-11-25 14:50 ` Edward Adam Davis
2024-11-25 16:23 ` syzbot
2024-11-25 23:58 ` [PATCH] Bluetooth: SCO: remove the redundant sco_conn_put Edward Adam Davis
2024-11-26 16:10 ` patchwork-bot+bluetooth [this message]
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=173263743076.458202.14094125770586556197.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=eadavis@qq.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=syzbot+489f78df4709ac2bfdd3@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox