From: Juan Quintela <quintela@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, lvivier@redhat.com,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] tests: Use real size for iov tests
Date: Wed, 23 Aug 2017 13:35:53 +0200 [thread overview]
Message-ID: <87r2w2ldnq.fsf@secure.mitica> (raw)
In-Reply-To: <20170823111832.GC19071@pxdev.xzpeter.org> (Peter Xu's message of "Wed, 23 Aug 2017 19:18:32 +0800")
Peter Xu <peterx@redhat.com> wrote:
> On Wed, Aug 23, 2017 at 10:39:00AM +0200, Juan Quintela wrote:
>> We were using -1 instead of the real size because the functions check
>> what is bigger, size in bytes or the size of the iov. Recent gcc's
>> barf at this.
>>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> ---
>> tests/test-iov.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/tests/test-iov.c b/tests/test-iov.c
>> index a22d71fd2c..819c410a51 100644
>> --- a/tests/test-iov.c
>> +++ b/tests/test-iov.c
>> @@ -81,17 +81,17 @@ static void test_to_from_buf_1(void)
>> * skip whole vector and process exactly 0 bytes */
>>
>> /* first set bytes [i..sz) to some "random" value */
>> - n = iov_memset(iov, niov, 0, 0xff, -1);
>> + n = iov_memset(iov, niov, 0, 0xff, sz);
>
> This one is not needed?
Not, but it is for consistence. iov_memset() has that property, that it
memset whatever is smaller, bytes parameter or iov size.
>> * with j in [i..sz]. */
>>
>> /* clear iovec */
>> - n = iov_memset(iov, niov, 0, 0xff, -1);
>> + n = iov_memset(iov, niov, 0, 0xff, sz);
>
> This one as well?
I decided to change all of them for consistence.
Using -1 is a trick that just happens to work for current
implementation, but it is a hack. and we have just after that an assert
with the real size that we want to copy. Just use them everywhere.
>
> Actually I think we can keep the two places above, but there seems to
> be a 3rd one below which is untouched. If we do change the two, maybe
> we'd better change the 3rd one as well.
Opps, didn't saw that other. With this changes it fixed all for me.
> Besides:
>
> Reviewed-by: Peter Xu <peterx@redhat.com>
Thanks, Juan.
>
>> g_assert(n == sz);
>>
>> /* copy bytes [i..j) from ibuf to iovec */
>> --
>> 2.13.5
>>
next prev parent reply other threads:[~2017-08-23 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 8:38 [Qemu-devel] [PATCH 0/2] Fix tests on recent gcc Juan Quintela
2017-08-23 8:39 ` [Qemu-devel] [PATCH 1/2] tests: Use real size for iov tests Juan Quintela
2017-08-23 11:18 ` Peter Xu
2017-08-23 11:35 ` Juan Quintela [this message]
2017-08-28 16:10 ` Thomas Huth
2017-08-30 9:45 ` Juan Quintela
2017-08-30 11:34 ` Juan Quintela
2017-08-23 8:39 ` [Qemu-devel] [PATCH 2/2] tests: Make acpid test compile Juan Quintela
2017-08-23 11:53 ` Dr. David Alan Gilbert
2017-08-28 14:41 ` Cédric Le Goater
2017-08-29 20:17 ` Eric Blake
2017-08-30 10:45 ` Daniel P. Berrange
2017-08-30 11:37 ` Juan Quintela
2017-08-30 10:51 ` Juan Quintela
2017-08-30 11:07 ` Daniel P. Berrange
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=87r2w2ldnq.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@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).