From: "Michał Narajowski" <michal.narajowski@codecoup.pl>
To: linux-bluetooth@vger.kernel.org
Cc: "Michał Narajowski" <michal.narajowski@codecoup.pl>
Subject: [PATCH BlueZ] monitor: Fix for incorrect len in L2CAP Enhanced Connection Req
Date: Thu, 28 May 2020 12:14:08 +0200 [thread overview]
Message-ID: <20200528101408.98400-1-michal.narajowski@codecoup.pl> (raw)
---
monitor/l2cap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/monitor/l2cap.c b/monitor/l2cap.c
index 41c766863..e571dbb61 100644
--- a/monitor/l2cap.c
+++ b/monitor/l2cap.c
@@ -1344,7 +1344,7 @@ static void sig_ecred_conn_req(const struct l2cap_frame *frame)
const struct bt_l2cap_pdu_ecred_conn_req *pdu = frame->data;
uint16_t scid;
- l2cap_frame_pull((void *)frame, frame, sizeof(pdu));
+ l2cap_frame_pull((void *)frame, frame, sizeof(*pdu));
print_psm(pdu->psm);
print_field("MTU: %u", le16_to_cpu(pdu->mtu));
--
2.25.1
next reply other threads:[~2020-05-28 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 10:14 Michał Narajowski [this message]
2020-05-28 10:36 ` [BlueZ] monitor: Fix for incorrect len in L2CAP Enhanced Connection Req bluez.test.bot
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=20200528101408.98400-1-michal.narajowski@codecoup.pl \
--to=michal.narajowski@codecoup.pl \
--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).