From: "Michael N. Moran" <mike@mnmoran.org>
To: linux-bluetooth@vger.kernel.org
Cc: "Michael N. Moran" <mike@mnmoran.org>
Subject: [PATCH BlueZ] meshctl truncates GATT MTU
Date: Sat, 28 Sep 2019 10:14:02 -0400 [thread overview]
Message-ID: <1569680043-2874-1-git-send-email-mike@mnmoran.org> (raw)
From: "Michael N. Moran" <mike@mnmoran.org>
This patch fixes a bug in meshctl that causes the
GATT MTU to be truncated resulting in incorrect
segmentation when the MTU is greater than 259.
Michael N. Moran (1):
The meshctl sock_write() max_len variable is declared as
uint8_t, which causes the calculation of the GATT MTU
to be truncated when the MTU (write_mtu) is greater
than 259. This error causes incorrect segmentation.
tools/mesh/gatt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2019-09-28 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 14:14 Michael N. Moran [this message]
2019-09-28 14:14 ` [PATCH BlueZ] The meshctl sock_write() max_len variable is declared as a uint8_t, which causes the calculation of the GATT MTU to be truncated when the MTU (write_mtu) is greater than 259. This error causes incorrect segmentation Michael N. Moran
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=1569680043-2874-1-git-send-email-mike@mnmoran.org \
--to=mike@mnmoran.org \
--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).