From: Steve Brown <sbrown@cortland.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH] Bluetooth: mesh: Correct segmentation logic
Date: Wed, 11 Oct 2017 13:06:24 -0600 [thread overview]
Message-ID: <20171011190624.2093-1-sbrown@cortland.com> (raw)
The decision whether to segment or not didn't consider the size of the MIC
diff --git a/mesh/net.c b/mesh/net.c
index 2d75c4f7d..96e82fe1c 100644
--- a/mesh/net.c
+++ b/mesh/net.c
@@ -2098,7 +2098,7 @@ bool net_access_layer_send(uint8_t ttl, uint16_t src, uint32_t dst,
if (!result)
return false;
- segN = SEG_MAX(len);
+ segN = SEG_MAX(len + sizeof(uint32_t));
/* Only one ACK required SAR message per destination at a time */
if (segN && IS_UNICAST(dst)) {
next reply other threads:[~2017-10-11 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 19:06 Steve Brown [this message]
2017-10-11 19:10 ` [PATCH] Bluetooth: mesh: Correct segmentation logic Gix, Brian
2017-10-11 19:21 ` Johan Hedberg
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=20171011190624.2093-1-sbrown@cortland.com \
--to=sbrown@cortland.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).