From: Eric Blake <eblake@redhat.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, den@virtuozzo.com,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v8] qemu-io: add pattern file for write command
Date: Wed, 7 Aug 2019 20:38:36 -0500 [thread overview]
Message-ID: <a8f813ea-d6ff-d26e-5afe-d683e5972e9c@redhat.com> (raw)
In-Reply-To: <20190807070631.9908-1-dplotnikov@virtuozzo.com>
[-- Attachment #1.1: Type: text/plain, Size: 2047 bytes --]
On 8/7/19 2:06 AM, Denis Plotnikov wrote:
> The patch allows to provide a pattern file for write
> command. There was no similar ability before.
>
> Signed-off-by: Denis Plotnikov <dplotnikov@virtuozzo.com>
> ---
>
> +static void *qemu_io_alloc_from_file(BlockBackend *blk, size_t len,
> + const char *file_name)
> +{
No comment on the usage of this function? Existing practice in this file
is not the best, but new code can do better.
> + char *buf, *buf_origin;
> + FILE *f = fopen(file_name, "r");
> + int pattern_len;
> +
> + if (!f) {
> + perror(file_name);
> + return NULL;
> + }
> +
> + if (qemuio_misalign) {
> + len += MISALIGN_OFFSET;
> + }
> +
> + buf_origin = buf = blk_blockalign(blk, len);
> +
> + if (qemuio_misalign) {
> + buf_origin += MISALIGN_OFFSET;
Here, you are changing where you point...
> + }
> +
> + pattern_len = fread(buf_origin, 1, len, f);
> +
> + if (ferror(f)) {
> + perror(file_name);
> + goto error;
> + }
...but if you fail here...
> +
> +error:
> + qemu_vfree(buf_origin);
...then you free the wrong pointer. This MUST use
qemu_io_free(buf_origin) (the same as write_f correctly does with the
misaligned pointer that you return on success).
> @@ -1051,8 +1114,9 @@ static int write_f(BlockBackend *blk, int argc, char **argv)
> return -EINVAL;
> }
>
> - if (zflag && Pflag) {
> - printf("-z and -P cannot be specified at the same time\n");
> + if ((int)zflag + (int)Pflag + (int)sflag > 1) {
The casts to int are not necessary. Adding two bools promotes to int
naturally.
> + printf("Only one of -z, -P, and -s"
> + "can be specified at the same time\n");
Missing a space; you don't want your user to see "and -scan be".
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-08-08 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 7:06 [Qemu-devel] [PATCH v8] qemu-io: add pattern file for write command Denis Plotnikov
2019-08-08 1:38 ` Eric Blake [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=a8f813ea-d6ff-d26e-5afe-d683e5972e9c@redhat.com \
--to=eblake@redhat.com \
--cc=den@virtuozzo.com \
--cc=dplotnikov@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).