From: patchwork-bot+bluetooth@kernel.org
To: Maxim Skokov <skokovmaksimevg@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
mikhail.v.gavrilov@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: RFCOMM: free the skb when the DLC has no owner
Date: Mon, 28 Sep 2026 17:30:06 +0000 [thread overview]
Message-ID: <179061660640.34603.9560704992810045042.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260915070119.45143-1-skokovmaksimevg@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, 15 Sep 2026 10:00:46 +0300 you wrote:
> rfcomm_recv_data() hands the skb to d->data_ready() and returns 0
> without freeing it, so the callback owns the skb from that point on.
> The tty implementation frees it when the DLC has been detached from its
> device:
>
> static void rfcomm_dev_data_ready(struct rfcomm_dlc *dlc,
> struct sk_buff *skb)
> {
> struct rfcomm_dev *dev = dlc->owner;
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: RFCOMM: free the skb when the DLC has no owner
https://git.kernel.org/bluetooth/bluetooth-next/c/9d1afbf60ed5
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-09-28 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:00 [PATCH v2] Bluetooth: RFCOMM: free the skb when the DLC has no owner Maxim Skokov
2026-09-15 12:57 ` [v2] " bluez.test.bot
2026-09-21 6:28 ` [PATCH v2] " Mikhail Gavrilov
2026-09-28 15:38 ` Maxim Skokov
2026-09-28 17: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=179061660640.34603.9560704992810045042.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=skokovmaksimevg@gmail.com \
--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 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.