Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-2183-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH 0/2] Bluetooth: btrtl: fix out of bounds memory access
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <170912883285.30835.6246607641130073666.git-patchwork-notify@kernel.org>
Date: Wed, 28 Feb 2024 14:00:32 +0000
References: <20240223213704.290849-1-andrej.skvortzov@gmail.com>
In-Reply-To: <20240223213704.290849-1-andrej.skvortzov@gmail.com>
To: Andrey Skvortsov <andrej.skvortzov@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, hildawu@realtek.com,
 alex_lu@realsil.com.cn, linux-bluetooth@vger.kernel.org,
 linux-kernel@vger.kernel.org, arnaud.ferraris@collabora.com

Hello:

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

On Sat, 24 Feb 2024 00:37:02 +0300 you wrote:
> The problem is detected by KASAN.
> btrtl driver uses private hci data to store 'struct btrealtek_data'.
> If btrtl driver is used with btusb, then memory for private hci data
> is allocated in btusb. But no private data is allocated after hci_dev,
> when btrtl is used with hci_h5.
> 
> These commits add memory allocation for hci_h5 case.
> 
> [...]

Here is the summary with links:
  - [1/2] Bluetooth: hci_h5: Add ability to allocate memory for private data
    https://git.kernel.org/bluetooth/bluetooth-next/c/171271f419d8
  - [2/2] Bluetooth: btrtl: fix out of bounds memory access
    https://git.kernel.org/bluetooth/bluetooth-next/c/d8f519096785

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