From: Eric Dumazet <edumazet@kernel.org>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Alexander Aring <alex.aring@gmail.com>,
Farhad Alemi <falemi@asu.edu>,
netdev@vger.kernel.org, edumazet@kernel.org
Subject: [PATCH net 0/2] ieee802154: 6lowpan: fix transmit address handling
Date: Mon, 28 Sep 2026 18:37:51 +0000 [thread overview]
Message-ID: <20260928183753.3550210-1-edumazet@kernel.org> (raw)
SEFCOM lab reported a warning in lowpan_compress_addr_64(),
triggered by an AF_PACKET socket sending on a lowpan device.
lowpan_header_create() stores the 802.15.4 addresses in the skb
headroom, where lowpan_xmit() cannot tell if they are valid.
It also reads the IPv6 header before AF_PACKET SOCK_DGRAM sockets
have copied it.
Patch 1 moves the neighbour short address lookup to lowpan_xmit().
Patch 2 pushes the destination address as an 8 byte pseudo header,
like IPoIB, and lets lowpan_xmit() compute the 802.15.4 addresses.
Eric Dumazet (2):
ieee802154: 6lowpan: look up the neighbour short address in
lowpan_xmit()
6lowpan: fix warning in lowpan_compress_addr_64()
net/ieee802154/6lowpan/6lowpan_i.h | 5 ++
net/ieee802154/6lowpan/core.c | 4 +-
net/ieee802154/6lowpan/tx.c | 128 ++++++++++++++---------------
3 files changed, 70 insertions(+), 67 deletions(-)
--
2.56.0.rc1.315.gc6ed9934b7-goog
next reply other threads:[~2026-09-28 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 18:37 Eric Dumazet [this message]
2026-09-28 18:37 ` [PATCH net 1/2] ieee802154: 6lowpan: look up the neighbour short address in lowpan_xmit() Eric Dumazet
2026-10-02 6:39 ` netdev-bot+sashiko
2026-10-02 7:15 ` Eric Dumazet
2026-09-28 18:37 ` [PATCH net 2/2] 6lowpan: fix warning in lowpan_compress_addr_64() Eric Dumazet
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=20260928183753.3550210-1-edumazet@kernel.org \
--to=edumazet@kernel.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=falemi@asu.edu \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.