From: patchwork-bot+bluetooth@kernel.org
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
Subject: Re: [PATCH 0/2] Bluetooth: btrtl: fix out of bounds memory access
Date: Wed, 28 Feb 2024 14:00:32 +0000 [thread overview]
Message-ID: <170912883285.30835.6246607641130073666.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240223213704.290849-1-andrej.skvortzov@gmail.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
prev parent reply other threads:[~2024-02-28 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 21:37 [PATCH 0/2] Bluetooth: btrtl: fix out of bounds memory access Andrey Skvortsov
2024-02-23 21:37 ` [PATCH 1/2] Bluetooth: hci_h5: Add ability to allocate memory for private data Andrey Skvortsov
2024-02-23 21:37 ` [PATCH 2/2] Bluetooth: btrtl: fix out of bounds memory access Andrey Skvortsov
2024-02-28 14:00 ` 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=170912883285.30835.6246607641130073666.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alex_lu@realsil.com.cn \
--cc=andrej.skvortzov@gmail.com \
--cc=arnaud.ferraris@collabora.com \
--cc=hildawu@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
/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;
as well as URLs for NNTP newsgroup(s).