From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Andrzej Zaborowski <balrog@zabor.org>,
Markus Armbruster <armbru@redhat.com>,
qemu-stable@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH v3 1/9] bt-sdp: fix broken uuids power-of-2 calculation
Date: Mon, 23 Mar 2015 15:29:23 +0000 [thread overview]
Message-ID: <1427124571-28598-2-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1427124571-28598-1-git-send-email-stefanha@redhat.com>
The binary search in sdp_uuid_match() only works when the number of
elements to search is a power of two.
lo = record->uuid;
hi = record->uuids;
while (hi >>= 1)
if (lo[hi] <= val)
lo += hi;
return *lo == val;
I noticed that the record->uuids calculation in
sdp_service_record_build() was suspect:
record->uuids = 1 << ffs(record->uuids - 1);
Unlike most ffs(val) - 1 users, the expression is ffs(val - 1)!
Actually ffs() is the wrong function to use for power-of-2. Use
pow2ceil() to achieve the correct effect. Now the record->uuid[] array
is sized correctly and the binary search in sdp_uuid_match() should
work.
I'm not sure how to run/test this code.
Cc: Andrzej Zaborowski <balrog@zabor.org>
Cc: qemu-stable@nongnu.org
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
hw/bt/sdp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/bt/sdp.c b/hw/bt/sdp.c
index 218e075..c903747 100644
--- a/hw/bt/sdp.c
+++ b/hw/bt/sdp.c
@@ -707,7 +707,7 @@ static void sdp_service_record_build(struct sdp_service_record_s *record,
len += sdp_attr_max_size(&def->attributes[record->attributes ++].data,
&record->uuids);
}
- record->uuids = 1 << ffs(record->uuids - 1);
+ record->uuids = pow2ceil(record->uuids);
record->attribute_list =
g_malloc0(record->attributes * sizeof(*record->attribute_list));
record->uuid =
--
2.1.0
next prev parent reply other threads:[~2015-03-23 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 15:29 [Qemu-devel] [PATCH v3 0/9] Convert ffs(3) to ctz32() Stefan Hajnoczi
2015-03-23 15:29 ` Stefan Hajnoczi [this message]
2015-03-23 15:29 ` [Qemu-devel] [PATCH v3 2/9] hw/arm/nseries: convert " Stefan Hajnoczi
2015-03-23 15:29 ` [Qemu-devel] [PATCH v3 3/9] uninorth: " Stefan Hajnoczi
2015-03-23 15:29 ` [Qemu-devel] [PATCH v3 4/9] Convert (ffs(val) - 1) to ctz32(val) Stefan Hajnoczi
2015-03-23 15:29 ` [Qemu-devel] [PATCH v3 5/9] Convert ffs() != 0 callers to ctz32() Stefan Hajnoczi
2015-03-23 15:29 ` [Qemu-devel] [PATCH v3 6/9] sd: convert sd_normal_command() ffs(3) call " Stefan Hajnoczi
2015-03-23 15:29 ` [Qemu-devel] [PATCH v3 7/9] omap_intc: convert ffs(3) to ctz32() in omap_inth_sir_update() Stefan Hajnoczi
2015-03-23 15:40 ` Paolo Bonzini
2015-03-24 13:36 ` Stefan Hajnoczi
2015-03-23 15:29 ` [Qemu-devel] [PATCH v3 8/9] os-win32: drop ffs(3) prototype Stefan Hajnoczi
2015-03-23 15:29 ` [Qemu-devel] [PATCH v3 9/9] checkpatch: complain about ffs(3) calls Stefan Hajnoczi
2015-03-25 13:09 ` [Qemu-devel] [PATCH v3 0/9] Convert ffs(3) to ctz32() Stefan Hajnoczi
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=1427124571-28598-2-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=balrog@zabor.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.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).