mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Joas Antonio dos Santos <joasantonio108@gmail.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org, brgl@kernel.org,
	linux-bluetooth@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_qca: clear qca_memdump when discarding dump packets
Date: Tue, 10 Nov 2026 16:10:17 +0000	[thread overview]
Message-ID: <179432701717.4062787.5293659281594260012.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110-hci-qca-memdump-v1-1-239974fc4944@gmail.com>

Hello:

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

On Tue, 10 Nov 2026 03:55:41 +0000 you wrote:
> From: Joas Antonio dos Santos <joasantonio108@gmail.com>
> 
> qca_controller_memdump() frees qca_memdump when a memdump packet with a
> non-zero sequence number arrives while QCA_MEMDUMP_COLLECTION is not
> set, but leaves qca->qca_memdump pointing at the freed object.
> 
> The next run of the work reads the stale pointer into its local
> variable, skips the allocation and uses the freed memory.  Another
> packet with a non-zero sequence number frees it a second time, and a
> packet with sequence number 0 writes ram_dump_size, current_seq_no and
> received_dump into it.
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_qca: clear qca_memdump when discarding dump packets
    https://git.kernel.org/bluetooth/bluetooth-next/c/45a25a1bfd26

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



      reply	other threads:[~2026-11-10 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  3:55 Joas Antonio dos Santos via B4 Relay
2026-11-10 16:10 ` 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=179432701717.4062787.5293659281594260012.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=brgl@kernel.org \
    --cc=joasantonio108@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®