Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-4184-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v3] Bluetooth: L2CAP: Fix slab-use-after-free in
 l2cap_connect()
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <171448683038.20667.12009081489317667942.git-patchwork-notify@kernel.org>
Date: Tue, 30 Apr 2024 14:20:30 +0000
References: <20240430063209.584244-1-iam@sung-woo.kim>
In-Reply-To: <20240430063209.584244-1-iam@sung-woo.kim>
To: Sungwoo Kim <iam@sung-woo.kim>
Cc: daveti@purdue.edu, dan.carpenter@linaro.org, marcel@holtmann.org,
 johan.hedberg@gmail.com, luiz.dentz@gmail.com,
 linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org

Hello:

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

On Tue, 30 Apr 2024 02:32:10 -0400 you wrote:
> Extend a critical section to prevent chan from early freeing.
> Also make the l2cap_connect() return type void. Nothing is using the
> returned value but it is ugly to return a potentially freed pointer.
> Making it void will help with backports because earlier kernels did use
> the return value. Now the compile will break for kernels where this
> patch is not a complete fix.
> 
> [...]

Here is the summary with links:
  - [v3] Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()
    https://git.kernel.org/bluetooth/bluetooth-next/c/6a39d26feb15

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