From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, Eric Blake <eblake@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Markus Armbruster <armbru@redhat.com>,
Sergey Fedorov <serge.fdrv@gmail.com>
Subject: [Qemu-devel] [PATCH v2 4/4] ARRAY_SIZE: check that argument is an array
Date: Wed, 18 Jan 2017 22:55:55 +0200 [thread overview]
Message-ID: <1484772931-16272-5-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1484772931-16272-1-git-send-email-mst@redhat.com>
It's a familiar pattern: some code uses ARRAY_SIZE, then refactoring
changes the argument from an array to a pointer to a dynamically
allocated buffer. Code keeps compiling but any ARRAY_SIZE calls now
return the size of the pointer divided by element size.
Let's add build time checks to ARRAY_SIZE before we allow more
of these in the code-base.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
include/qemu/osdep.h | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
index 689f253..24bfda0 100644
--- a/include/qemu/osdep.h
+++ b/include/qemu/osdep.h
@@ -199,7 +199,13 @@ extern int daemon(int, int);
#endif
#ifndef ARRAY_SIZE
-#define ARRAY_SIZE(x) (sizeof(x) / sizeof((x)[0]))
+/*
+ * &(x)[0] is always a pointer - if it's same type as x then the argument is a
+ * pointer, not an array as expected.
+ */
+#define ARRAY_SIZE(x) ((sizeof(x) / sizeof((x)[0])) + QEMU_BUILD_BUG_ON_ZERO( \
+ __builtin_types_compatible_p(typeof(x), \
+ typeof(&(x)[0]))))
#endif
int qemu_daemon(int nochdir, int noclose);
--
MST
next prev parent reply other threads:[~2017-01-18 20:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 20:55 [Qemu-devel] [PATCH v2 0/4] virtio: ARRAY_SIZE fixups Michael S. Tsirkin
2017-01-18 20:55 ` [Qemu-devel] [PATCH v2 1/4] virtio: fix up max size checks Michael S. Tsirkin
2017-01-19 9:46 ` Cornelia Huck
2017-01-18 20:55 ` [Qemu-devel] [PATCH v2 2/4] compiler: drop ; after BUILD_BUG_ON Michael S. Tsirkin
2017-01-18 21:04 ` Peter Maydell
2017-01-18 21:16 ` Michael S. Tsirkin
2017-01-18 21:23 ` Michael S. Tsirkin
2017-01-18 21:53 ` Peter Maydell
2017-01-19 8:09 ` Markus Armbruster
2017-01-18 20:55 ` [Qemu-devel] [PATCH v2 3/4] compiler: expression version of QEMU_BUILD_BUG_ON Michael S. Tsirkin
2017-01-19 8:12 ` Markus Armbruster
2017-01-19 10:01 ` Paolo Bonzini
2017-01-19 13:33 ` Markus Armbruster
2017-01-19 19:25 ` Michael S. Tsirkin
2017-01-19 20:58 ` Eric Blake
2017-01-19 21:02 ` Michael S. Tsirkin
2017-01-20 7:21 ` Markus Armbruster
2017-01-20 17:50 ` Michael S. Tsirkin
2017-01-19 21:01 ` Michael S. Tsirkin
2017-01-18 20:55 ` Michael S. Tsirkin [this message]
2017-01-19 8:20 ` [Qemu-devel] [PATCH v2 4/4] ARRAY_SIZE: check that argument is an array Markus Armbruster
2017-01-19 11:00 ` Peter Maydell
2017-01-19 14:53 ` Eric Blake
2017-01-19 15:06 ` Michael S. Tsirkin
2017-01-18 21:06 ` [Qemu-devel] [PATCH v2 0/4] virtio: ARRAY_SIZE fixups no-reply
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=1484772931-16272-5-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=serge.fdrv@gmail.com \
/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).