From: Paolo Bonzini <pbonzini@redhat.com>
To: Shmulik Ladkani <shmulik.ladkani@oracle.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org
Cc: Dmitry Fleytman <dmitry@daynix.com>,
Jason Wang <jasowang@redhat.com>,
Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
Subject: Re: [Qemu-devel] [PATCH] util: Relax assertion in iov_copy()
Date: Mon, 1 Aug 2016 15:47:39 +0200 [thread overview]
Message-ID: <2e4aeb04-c23e-dada-779d-f0ef9e1eac70@redhat.com> (raw)
In-Reply-To: <1469447015-2276-1-git-send-email-shmulik.ladkani@oracle.com>
On 25/07/2016 13:43, Shmulik Ladkani wrote:
> From: Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
>
> In cases where iov_copy() is passed with zero 'bytes' argument and a
> non-zero 'offset' argument, nothing gets copied - as expected.
>
> However since no copy iterations are performed, 'offset' is left
> unaltered, leading to the final assert(offset == 0) to fail.
>
> Relax the assertion: if j (number of dst elements assigned) is zero, no
> need to err.
>
> Only if j!=0 (some dst elements assigned) AND offset!=0 we should err.
This is actually intended; the comment in qemu_iovec_concat_iov says why:
assert(soffset == 0); /* offset beyond end of src */
so the pedantic fix could be (if I understand the issue correctly) to
check for "offset || bytes" in the for condition. This is similar to
what the other functions do (e.g. iov_from_buf_full). The performance
effect should practically be absent.
Paolo
> Signed-off-by: Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
> ---
> util/iov.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Flow that led to the assertion was:
> net_tx_pkt_rebuild_payload()
> iov_copy(... , pkt->payload_len)
>
> where pkt->payload_len was correctly calculated to be 0 (a packet
> carrying just ipv4 header, without any payload).
>
> An alternative is to place the below code, early in iov_copy():
> if (!bytes)
> return 0;
>
> diff --git a/util/iov.c b/util/iov.c
> index 003fcce..17de52d 100644
> --- a/util/iov.c
> +++ b/util/iov.c
> @@ -260,7 +260,7 @@ unsigned iov_copy(struct iovec *dst_iov, unsigned int dst_iov_cnt,
> bytes -= len;
> offset = 0;
> }
> - assert(offset == 0);
> + assert(j == 0 || offset == 0);
> return j;
> }
>
>
prev parent reply other threads:[~2016-08-01 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 11:43 [Qemu-devel] [PATCH] util: Relax assertion in iov_copy() Shmulik Ladkani
2016-07-27 4:20 ` Michael S. Tsirkin
2016-08-01 13:47 ` Paolo Bonzini [this message]
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=2e4aeb04-c23e-dada-779d-f0ef9e1eac70@redhat.com \
--to=pbonzini@redhat.com \
--cc=dmitry@daynix.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shmulik.ladkani@oracle.com \
--cc=shmulik.ladkani@ravellosystems.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).