From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, inga.stotland@intel.com, rafal.gajda@silvair.com
Subject: [PATCH BlueZ v4 0/5] mesh: Add NVM storage of Replay Protection List
Date: Tue, 28 Jan 2020 18:32:53 -0800 [thread overview]
Message-ID: <20200129023258.10004-1-brian.gix@intel.com> (raw)
Version 4: Style guide fixes from Inga (patch 5/5).
Version 3: Fix problem found by Rafał relating to the handling of
sequence numbers of messages being handled internally (loop-backs),
which were being rejected by the Replay Protection List (please see
patch 3/5).
Version 2: Fix path construction code when first reading RPL from NVM
An oversight led to losing our Replay Protection List with every
re-boot. This patch-set makes a number of Replay Protect List
modifications that culminate in adding rpl.c/h, which stores the latest
iv_index/sequence values for each node that handles an incoming packet.
The first 4 patches, does some maintenance required to handle RPL
according the the Mesh Specification.
Brian Gix (5):
mesh: Relocate tree deletion to util.c/h
mesh: Move Replay Protection to mesh/net.c
mesh: Clean-up unneeded Sequence Number increments
mesh: Apply Replay Protection to all incoming packets
mesh: Add NVM storage of Replay Protection
Makefile.mesh | 1 +
mesh/appkey.c | 102 ---------------
mesh/appkey.h | 3 -
mesh/mesh-config-json.c | 20 +--
mesh/model.c | 16 +--
mesh/net.c | 128 +++++++++++++++---
mesh/net.h | 3 +
mesh/rpl.c | 278 ++++++++++++++++++++++++++++++++++++++++
mesh/rpl.h | 30 +++++
mesh/util.c | 25 ++++
mesh/util.h | 1 +
11 files changed, 457 insertions(+), 150 deletions(-)
create mode 100644 mesh/rpl.c
create mode 100644 mesh/rpl.h
--
2.21.1
next reply other threads:[~2020-01-29 2:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 2:32 Brian Gix [this message]
2020-01-29 2:32 ` [PATCH BlueZ v4 1/5] mesh: Relocate tree deletion to util.c/h Brian Gix
2020-01-29 2:32 ` [PATCH BlueZ v4 2/5] mesh: Move Replay Protection to mesh/net.c Brian Gix
2020-01-29 2:32 ` [PATCH BlueZ v4 3/5] mesh: Clean-up unneeded Sequence Number increments Brian Gix
2020-01-29 2:32 ` [PATCH BlueZ v4 4/5] mesh: Apply Replay Protection to all incoming packets Brian Gix
2020-01-29 2:32 ` [PATCH BlueZ v4 5/5] mesh: Add NVM storage of Replay Protection Brian Gix
2020-01-29 12:17 ` Rafal Gajda
2020-01-29 15:06 ` Gix, Brian
2020-01-30 8:55 ` Rafal Gajda
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=20200129023258.10004-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=rafal.gajda@silvair.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).