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 v5 3/5] mesh: Clean-up unneeded Sequence Number increments
Date: Wed, 29 Jan 2020 09:07:30 -0800 [thread overview]
Message-ID: <20200129170732.1607-4-brian.gix@intel.com> (raw)
In-Reply-To: <20200129170732.1607-1-brian.gix@intel.com>
Scrub of Sequence Number handling of OB messages to account for in-node
delivery of segmented messages, so that each discrete message has a
unique sequence number for the RPL.
---
mesh/net.c | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/mesh/net.c b/mesh/net.c
index 71ff2cea0..9567d947e 100644
--- a/mesh/net.c
+++ b/mesh/net.c
@@ -3043,14 +3043,19 @@ static bool send_seg(struct mesh_net *net, struct mesh_sar *msg, uint8_t segO)
uint8_t segN = SEG_MAX(msg->len);
uint16_t seg_off = SEG_OFF(segO);
uint32_t key_id = 0;
- uint32_t seq_num = mesh_net_next_seq_num(net);
+ uint32_t seq_num;
if (segN) {
+ /* Send each segment on unique seq_num */
+ seq_num = mesh_net_next_seq_num(net);
+
if (msg->len - seg_off > SEG_OFF(1))
seg_len = SEG_OFF(1);
else
seg_len = msg->len - seg_off;
} else {
+ /* Send on same seq_num used for Access Layer */
+ seq_num = msg->seqAuth;
seg_len = msg->len;
}
@@ -3185,7 +3190,7 @@ bool mesh_net_app_send(struct mesh_net *net, bool frnd_cred, uint16_t src,
/* First enqueue to any Friends and internal models */
result = msg_rxed(net, false, iv_index, ttl,
- seq + seg_max,
+ seq,
net_idx,
src, dst,
key_aid,
@@ -3196,12 +3201,8 @@ bool mesh_net_app_send(struct mesh_net *net, bool frnd_cred, uint16_t src,
* or delivered to one of our Unicast addresses we are done
*/
if ((result && IS_UNICAST(dst)) || src == dst ||
- (dst >= net->src_addr && dst <= net->last_addr)) {
- /* Adjust our seq_num for "virtual" delivery */
- net->seq_num += seg_max;
- mesh_net_next_seq_num(net);
+ (dst >= net->src_addr && dst <= net->last_addr))
return true;
- }
/* If Segmented, Cancel any OB segmented message to same DST */
if (seg_max) {
@@ -3226,7 +3227,7 @@ bool mesh_net_app_send(struct mesh_net *net, bool frnd_cred, uint16_t src,
}
payload->iv_index = mesh_net_get_iv_index(net);
- payload->seqAuth = net->seq_num;
+ payload->seqAuth = seq;
result = true;
if (!IS_UNICAST(dst) && seg_max) {
--
2.21.1
next prev parent reply other threads:[~2020-01-29 17:07 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 ` Brian Gix [this message]
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 ` [PATCH BlueZ v5 0/5] mesh: Add NVM storage of Replay Protection List Gix, Brian
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=20200129170732.1607-4-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).