From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
johan.hedberg@gmail.com, luiz.dentz@gmail.com,
linux-kernel@vger.kernel.org, pmenzel@molgen.mpg.de
Subject: Re: [PATCH v2 1/5] Bluetooth: 6lowpan: reset link-local header on ipv6 recv path
Date: Fri, 07 Nov 2025 19:10:08 +0000 [thread overview]
Message-ID: <176254260850.1132280.1139292633245300172.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <467024bf1ba60184bff304d23de33abb0ed2384f.1762194056.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 3 Nov 2025 20:29:46 +0200 you wrote:
> Bluetooth 6lowpan.c netdev has header_ops, so it must set link-local
> header for RX skb, otherwise things crash, eg. with AF_PACKET SOCK_RAW
>
> Add missing skb_reset_mac_header() for uncompressed ipv6 RX path.
>
> For the compressed one, it is done in lowpan_header_decompress().
>
> [...]
Here is the summary with links:
- [v2,1/5] Bluetooth: 6lowpan: reset link-local header on ipv6 recv path
https://git.kernel.org/bluetooth/bluetooth-next/c/7de8dc9b760c
- [v2,2/5] Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion
https://git.kernel.org/bluetooth/bluetooth-next/c/c7409a88d204
- [v2,3/5] Bluetooth: L2CAP: export l2cap_chan_hold for modules
https://git.kernel.org/bluetooth/bluetooth-next/c/35d11c1cf51d
- [v2,4/5] Bluetooth: 6lowpan: Don't hold spin lock over sleeping functions
https://git.kernel.org/bluetooth/bluetooth-next/c/e1cd2d7db0bf
- [v2,5/5] Bluetooth: 6lowpan: add missing l2cap_chan_lock()
https://git.kernel.org/bluetooth/bluetooth-next/c/fde5b271c88f
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:[~2025-11-07 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 18:29 Pauli Virtanen
2025-11-03 18:29 ` [PATCH v2 2/5] Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion Pauli Virtanen
2025-11-03 18:29 ` [PATCH v2 3/5] Bluetooth: L2CAP: export l2cap_chan_hold for modules Pauli Virtanen
2025-11-04 10:44 ` Paul Menzel
2025-11-03 18:29 ` [PATCH v2 4/5] Bluetooth: 6lowpan: Don't hold spin lock over sleeping functions Pauli Virtanen
2025-11-03 18:29 ` [PATCH v2 5/5] Bluetooth: 6lowpan: add missing l2cap_chan_lock() Pauli Virtanen
2025-11-07 19: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=176254260850.1132280.1139292633245300172.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pav@iki.fi \
--cc=pmenzel@molgen.mpg.de \
/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®