From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: patrik.flykt@linux.intel.com, jukka.rissanen@linux.intel.com,
stefan@osg.samsung.com, aar@pengutronix.de,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH v5 0/6] Bluetooth: 6LoWPAN: Fix lladdr length
Date: Fri, 24 Feb 2017 14:14:34 +0200 [thread overview]
Message-ID: <20170224121440.32269-1-luiz.dentz@gmail.com> (raw)
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
These patches fixes lladdr length to be 6 bytes long and not 8 which cause
neighbor advertisement to be sent with wrong lladdr including FF:FE filler
bytes for eui64.
Note: This does not fix some of the existing crashes which I hope to address
in a different set.
v2: Make all code paths that generate a link-local from lladdr use the same
code.
v3: Use lowpan_iphc_uncompress_eui48_lladdr to generate the remote ip address.
v4: Handle comments from Stefan Schmidt.
v5: Add patch to fix IID format for Bluetooth
Alexander Aring (2):
6lowpan: iphc: override l2 packet information
ipv6: addrconf: fix 48 bit 6lowpan autoconfiguration
Luiz Augusto von Dentz (2):
6lowpan: Use netdev addr_len to determine lladdr len
6lowpan: Fix IID format for Bluetooth
Patrik Flykt (2):
bluetooth: Set 6 byte device addresses
6lowpan: Set MAC address length according to LOWPAN_LLTYPE
include/net/6lowpan.h | 15 ++++++
net/6lowpan/core.c | 11 +++-
net/6lowpan/iphc.c | 57 +++++++++++++++++----
net/bluetooth/6lowpan.c | 130 ++++++++----------------------------------------
net/ipv6/addrconf.c | 17 +++++--
5 files changed, 104 insertions(+), 126 deletions(-)
--
2.9.3
next reply other threads:[~2017-02-24 12:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 12:14 Luiz Augusto von Dentz [this message]
2017-02-24 12:14 ` [PATCH v5 1/6] bluetooth: Set 6 byte device addresses Luiz Augusto von Dentz
2017-02-24 12:14 ` [PATCH v5 2/6] 6lowpan: Set MAC address length according to LOWPAN_LLTYPE Luiz Augusto von Dentz
[not found] ` <20170224121440.32269-1-luiz.dentz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-24 12:14 ` [PATCH v5 3/6] 6lowpan: iphc: override l2 packet information Luiz Augusto von Dentz
2017-02-24 12:14 ` [PATCH v5 4/6] ipv6: addrconf: fix 48 bit 6lowpan autoconfiguration Luiz Augusto von Dentz
2017-02-26 6:38 ` Alexander Aring
2017-03-01 11:09 ` Luiz Augusto von Dentz
2017-02-24 12:14 ` [PATCH v5 5/6] 6lowpan: Use netdev addr_len to determine lladdr len Luiz Augusto von Dentz
[not found] ` <20170224121440.32269-6-luiz.dentz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-27 7:13 ` Alexander Aring
[not found] ` <39321f06-c013-1e8f-efd1-2e230659535b-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-02-27 7:24 ` Alexander Aring
2017-02-24 12:14 ` [PATCH v5 6/6] 6lowpan: Fix IID format for Bluetooth Luiz Augusto von Dentz
[not found] ` <20170224121440.32269-7-luiz.dentz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-24 14:00 ` Stefan Schmidt
2017-02-26 6:05 ` Alexander Aring
[not found] ` <afc9cb44-edb6-287b-ce1d-da1c0974b5fa-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-02-26 6:25 ` Alexander Aring
2017-02-28 9:13 ` Jukka Rissanen
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=20170224121440.32269-1-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.com \
--cc=aar@pengutronix.de \
--cc=jukka.rissanen@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patrik.flykt@linux.intel.com \
--cc=stefan@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).