From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "Stotland, Inga" <inga.stotland@intel.com>,
"rafal.gajda@silvair.com" <rafal.gajda@silvair.com>
Subject: Re: [PATCH BlueZ v5 0/5] mesh: Add NVM storage of Replay Protection List
Date: Thu, 30 Jan 2020 19:34:10 +0000 [thread overview]
Message-ID: <73eed33a0d242713baa0fa58920a07ee61df879b.camel@intel.com> (raw)
In-Reply-To: <20200129170732.1607-1-brian.gix@intel.com>
Patchset Applied
On Wed, 2020-01-29 at 09:07 -0800, Brian Gix wrote:
> Version 5: Extra clean-up fixes added for malformed RPL trees, and
> iv_index dirs created "as needed" instead of at RPL initialization.
> (patch 5/5)
>
> 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 | 289 ++++++++++++++++++++++++++++++++++++++++
> mesh/rpl.h | 30 +++++
> mesh/util.c | 25 ++++
> mesh/util.h | 1 +
> 11 files changed, 468 insertions(+), 150 deletions(-)
> create mode 100644 mesh/rpl.c
> create mode 100644 mesh/rpl.h
>
prev parent reply other threads:[~2020-01-30 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 17:07 [PATCH BlueZ v5 0/5] mesh: Add NVM storage of Replay Protection List Brian Gix
2020-01-29 17:07 ` [PATCH BlueZ v5 1/5] mesh: Relocate tree deletion to util.c/h Brian Gix
2020-01-29 17:07 ` [PATCH BlueZ v5 2/5] mesh: Move Replay Protection to mesh/net.c Brian Gix
2020-01-29 17:07 ` [PATCH BlueZ v5 3/5] mesh: Clean-up unneeded Sequence Number increments Brian Gix
2020-01-29 17:07 ` [PATCH BlueZ v5 4/5] mesh: Apply Replay Protection to all incoming packets Brian Gix
2020-01-29 17:07 ` [PATCH BlueZ v5 5/5] mesh: Add NVM storage of Replay Protection Brian Gix
2020-01-30 19:34 ` Gix, Brian [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=73eed33a0d242713baa0fa58920a07ee61df879b.camel@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).