From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ 1/6] shared/csip: Fix returning invalid data to attribute Size reads
Date: Mon, 2 Oct 2023 16:13:05 -0700 [thread overview]
Message-ID: <20231002231311.3104749-1-luiz.dentz@gmail.com> (raw)
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
The attribute Size value is stored in the size_val not on size member
which represents the attribute object.
---
src/shared/csip.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/shared/csip.c b/src/shared/csip.c
index 04a8d542b390..24d5d6a323bd 100644
--- a/src/shared/csip.c
+++ b/src/shared/csip.c
@@ -291,8 +291,8 @@ static void csis_size_read(struct gatt_db_attribute *attrib,
struct bt_csis *csis = user_data;
struct iovec iov;
- iov.iov_base = &csis->size;
- iov.iov_len = sizeof(csis->size);
+ iov.iov_base = &csis->size_val;
+ iov.iov_len = sizeof(csis->size_val);
gatt_db_attribute_read_result(attrib, id, 0, iov.iov_base,
iov.iov_len);
--
2.41.0
next reply other threads:[~2023-10-02 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 23:13 Luiz Augusto von Dentz [this message]
2023-10-02 23:13 ` [PATCH BlueZ 2/6] shared/csip: Fix not requiring encryption Luiz Augusto von Dentz
2023-10-02 23:13 ` [PATCH BlueZ 3/6] shared/csip: Fix not always reading SIRK value Luiz Augusto von Dentz
2023-10-02 23:13 ` [PATCH BlueZ 4/6] device: Add btd_device_get_ltk Luiz Augusto von Dentz
2023-10-02 23:13 ` [PATCH BlueZ 5/6] csip: Add support for SIRK encryption Luiz Augusto von Dentz
2023-10-02 23:13 ` [PATCH BlueZ 6/6] main.conf: Fix default of CSIS.encrypt Luiz Augusto von Dentz
2023-10-03 1:50 ` [BlueZ,1/6] shared/csip: Fix returning invalid data to attribute Size reads bluez.test.bot
2023-10-03 23:20 ` [PATCH BlueZ 1/6] " patchwork-bot+bluetooth
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=20231002231311.3104749-1-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.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).