From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: kvm@vger.kernel.org, pbonzini@redhat.com
Cc: frankja@linux.ibm.com, thuth@redhat.com, david@redhat.com,
drjones@redhat.com, jmattson@google.com,
sean.j.christopherson@intel.com
Subject: [kvm-unit-tests PATCH v1 2/2] lib/alloc_page: Fix compilation issue on 32bit archs
Date: Tue, 14 Jul 2020 13:09:19 +0200 [thread overview]
Message-ID: <20200714110919.50724-3-imbrenda@linux.ibm.com> (raw)
In-Reply-To: <20200714110919.50724-1-imbrenda@linux.ibm.com>
The assert in lib/alloc_page is hardcoded to long, and size_t is just
an int on 32 bit architectures.
Adding a cast makes the compiler happy.
Fixes: 73f4b202beb39 ("lib/alloc_page: change some parameter types")
Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
---
lib/alloc_page.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/lib/alloc_page.c b/lib/alloc_page.c
index fa3c527..617b003 100644
--- a/lib/alloc_page.c
+++ b/lib/alloc_page.c
@@ -29,11 +29,12 @@ void free_pages(void *mem, size_t size)
assert_msg((unsigned long) mem % PAGE_SIZE == 0,
"mem not page aligned: %p", mem);
- assert_msg(size % PAGE_SIZE == 0, "size not page aligned: %#lx", size);
+ assert_msg(size % PAGE_SIZE == 0, "size not page aligned: %#lx",
+ (unsigned long)size);
assert_msg(size == 0 || (uintptr_t)mem == -size ||
(uintptr_t)mem + size > (uintptr_t)mem,
- "mem + size overflow: %p + %#lx", mem, size);
+ "mem + size overflow: %p + %#lx", mem, (unsigned long)size);
if (size == 0) {
freelist = NULL;
--
2.26.2
next prev parent reply other threads:[~2020-07-14 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 11:09 [kvm-unit-tests PATCH v1 0/2] Fix some compilation issues on 32bit Claudio Imbrenda
2020-07-14 11:09 ` [kvm-unit-tests PATCH v1 1/2] x86/cstart: Fix compilation issue in 32 bit mode Claudio Imbrenda
2020-07-14 11:09 ` Claudio Imbrenda [this message]
2020-07-14 11:20 ` [kvm-unit-tests PATCH v1 2/2] lib/alloc_page: Fix compilation issue on 32bit archs Thomas Huth
2020-07-14 11:41 ` Claudio Imbrenda
2020-07-14 14:05 ` Sean Christopherson
2020-07-14 14:11 ` Claudio Imbrenda
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=20200714110919.50724-3-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=thuth@redhat.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