All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
	chethan.tumkur.narayan@intel.com
Subject: Re: [PATCH v1] Bluetooth: btintel_pcie: validate TX skb length in send_sync
Date: Tue, 08 Sep 2026 16:30:10 +0000	[thread overview]
Message-ID: <178888501048.3627954.5315062891707768596.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260908095658.729390-1-chandrashekar.devegowda@intel.com>

Hello:

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

On Tue,  8 Sep 2026 15:26:58 +0530 you wrote:
> btintel_pcie_prepare_tx() copies skb->len bytes into a fixed
> BTINTEL_PCIE_BUFFER_SIZE (4096) DMA slot via an unchecked memcpy.
> Oversized packets are currently rejected only in
> btintel_pcie_send_frame(); any future caller of
> btintel_pcie_send_sync() would silently overflow the DMA buffer.
> 
> Add the bounds check in btintel_pcie_send_sync() itself, right
> before skb_push() and the DMA copy.
> 
> [...]

Here is the summary with links:
  - [v1] Bluetooth: btintel_pcie: validate TX skb length in send_sync
    https://git.kernel.org/bluetooth/bluetooth-next/c/88906c2d5b21

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-08 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  9:56 [PATCH v1] Bluetooth: btintel_pcie: validate TX skb length in send_sync Chandrashekar Devegowda
2026-09-08 15:49 ` [v1] " bluez.test.bot
2026-09-08 16: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=178888501048.3627954.5315062891707768596.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=chandrashekar.devegowda@intel.com \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ravishankar.srivatsa@intel.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.