All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Bluetooth: ISO: Fix parent socket leak in iso_conn_ready()
Date: Mon, 14 Sep 2026 14:30:13 +0000	[thread overview]
Message-ID: <178939621337.604238.10918376880914591840.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910181206.1558734-1-luiz.dentz@gmail.com>

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu, 10 Sep 2026 14:12:05 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> iso_get_sock() returns the parent socket with a reference held, which is
> dropped by sock_put() once the child socket has been set up. The error
> path taken when iso_sock_alloc() fails only calls release_sock() and
> returns, leaking the reference and thus the parent socket itself.
> 
> [...]

Here is the summary with links:
  - [v2,1/2] Bluetooth: ISO: Fix parent socket leak in iso_conn_ready()
    https://git.kernel.org/bluetooth/bluetooth-next/c/dc9dac316171
  - [v2,2/2] Bluetooth: ISO: set BT_LISTEN before requesting a BIG sync
    https://git.kernel.org/bluetooth/bluetooth-next/c/21db869e228f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-14 14:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 18:12 [PATCH v2 1/2] Bluetooth: ISO: Fix parent socket leak in iso_conn_ready() Luiz Augusto von Dentz
2026-09-10 18:12 ` [PATCH v2 2/2] Bluetooth: ISO: set BT_LISTEN before requesting a BIG sync Luiz Augusto von Dentz
2026-09-10 20:58 ` [v2,1/2] Bluetooth: ISO: Fix parent socket leak in iso_conn_ready() bluez.test.bot
2026-09-14 14:30 ` 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=178939621337.604238.10918376880914591840.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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.