All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, thuth@redhat.com, borntraeger@de.ibm.com
Subject: Re: [kvm-unit-tests PATCH] s390x: Fix selftest malloc check
Date: Wed, 23 Oct 2019 10:45:49 +0200	[thread overview]
Message-ID: <cce26d3f-83d5-09e8-7a22-de37a2d117dc@linux.ibm.com> (raw)
In-Reply-To: <b5363884-7360-ffc4-b572-f1942cbfae20@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1494 bytes --]

On 10/23/19 10:41 AM, David Hildenbrand wrote:
> On 23.10.19 10:40, Janosch Frank wrote:
>> Commit c09c54c ("lib: use an argument which doesn't require default
>> argument promotion") broke the selftest. Let's fix it by converting
>> the binary operations to bool.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>>   s390x/selftest.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/s390x/selftest.c b/s390x/selftest.c
>> index f4acdc4..9cd6943 100644
>> --- a/s390x/selftest.c
>> +++ b/s390x/selftest.c
>> @@ -49,9 +49,9 @@ static void test_malloc(void)
>>   	*tmp2 = 123456789;
>>   	mb();
>>   
>> -	report("malloc: got vaddr", (uintptr_t)tmp & 0xf000000000000000ul);
>> +	report("malloc: got vaddr", !!((uintptr_t)tmp & 0xf000000000000000ul));
>>   	report("malloc: access works", *tmp == 123456789);
>> -	report("malloc: got 2nd vaddr", (uintptr_t)tmp2 & 0xf000000000000000ul);
>> +	report("malloc: got 2nd vaddr", !!((uintptr_t)tmp2 & 0xf000000000000000ul));
>>   	report("malloc: access works", (*tmp2 == 123456789));
>>   	report("malloc: addresses differ", tmp != tmp2);
>>   
>>
> 
> See
> 
> https://lore.kernel.org/kvm/CAGG=3QUdVBg5JArMaBcRbBLrHqLLCpAcrtvgT4q1h0V7SHbbEQ@mail.gmail.com/T/
> 

I completely missed that patch and only looked for fixpatches on the
list -_-

If possible CC me if something like this turns up, so I don't have the
CI flashing red lights at me unexpectedly :)



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-10-23  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  8:40 [kvm-unit-tests PATCH] s390x: Fix selftest malloc check Janosch Frank
2019-10-23  8:41 ` David Hildenbrand
2019-10-23  8:45   ` Janosch Frank [this message]
2019-10-23  8:47     ` David Hildenbrand

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=cce26d3f-83d5-09e8-7a22-de37a2d117dc@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.