From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: 6lowpan: Always consume the skb in chan_recv_cb
Date: Mon, 16 Nov 2026 19:50:06 +0000 [thread overview]
Message-ID: <179485860627.3856541.8397441841963712517.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261113161952.926201-1-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 13 Nov 2026 11:19:52 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> The l2cap_chan_ops recv callback takes ownership of the skb on success and
> leaves it to the caller on failure. chan_recv_cb() violates this: when
> recv_pkt() fails it returns -EAGAIN even though skb_share_check() may
> already have dropped the caller's reference to a shared skb and replaced
> it with a clone. The L2CAP caller then calls kfree_skb() on the original
> skb, over-releasing it, while the clone is leaked.
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: 6lowpan: Always consume the skb in chan_recv_cb
https://git.kernel.org/bluetooth/bluetooth-next/c/0d8f6981f55e
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-11-16 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 16:19 [PATCH v1] Bluetooth: 6lowpan: Always consume the skb in chan_recv_cb Luiz Augusto von Dentz
2026-11-13 17:03 ` [v1] " bluez.test.bot
2026-11-16 19:50 ` 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=179485860627.3856541.8397441841963712517.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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.