From: patchwork-bot+bluetooth@kernel.org
To: Heitor Alves de Siqueira <halves@igalia.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, willemb@google.com, pav@iki.fi,
luiz.von.dentz@intel.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-dev@igalia.com,
syzbot+7ff4013eabad1407b70a@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: purge error queues in socket destructors
Date: Wed, 11 Feb 2026 19:40:08 +0000 [thread overview]
Message-ID: <177083880807.688115.2802433045954977794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260211-bt-purge-error-queue-v1-1-42159dd7bb28@igalia.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 11 Feb 2026 15:03:35 -0300 you wrote:
> When TX timestamping is enabled via SO_TIMESTAMPING, SKBs may be queued
> into sk_error_queue and will stay there until consumed. If userspace never
> gets to read the timestamps, or if the controller is removed unexpectedly,
> these SKBs will leak.
>
> Fix by adding skb_queue_purge() calls for sk_error_queue in affected
> bluetooth destructors. RFCOMM does not currently use sk_error_queue.
>
> [...]
Here is the summary with links:
- Bluetooth: purge error queues in socket destructors
https://git.kernel.org/bluetooth/bluetooth-next/c/d5e3243e55d7
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:[~2026-02-11 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 18:03 [PATCH] Bluetooth: purge error queues in socket destructors Heitor Alves de Siqueira
2026-02-11 19:40 ` 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=177083880807.688115.2802433045954977794.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=halves@igalia.com \
--cc=johan.hedberg@gmail.com \
--cc=kernel-dev@igalia.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=pav@iki.fi \
--cc=stable@vger.kernel.org \
--cc=syzbot+7ff4013eabad1407b70a@syzkaller.appspotmail.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox