qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	"Richard W . M . Jones" <rjones@redhat.com>,
	Jeff Cody <jcody@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] block/ssh: Make ssh_grow_file() blocking
Date: Wed, 14 Feb 2018 15:11:15 -0600	[thread overview]
Message-ID: <eb2c00e1-eae0-7d71-b4dc-0df0054a3fb2@redhat.com> (raw)
In-Reply-To: <20180214204915.7980-3-mreitz@redhat.com>

On 02/14/2018 02:49 PM, Max Reitz wrote:
> At runtime (that is, during a future ssh_truncate()), the SSH session is
> non-blocking.  However, ssh_truncate() (or rather, bdrv_truncate() in
> general) is not a coroutine, so this resize operation needs to block.
> 
> For ssh_create(), that is fine, too; the session is never set to
> non-blocking anyway.
> 
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
>   block/ssh.c | 7 +++++++
>   1 file changed, 7 insertions(+)
> 
> diff --git a/block/ssh.c b/block/ssh.c
> index 964e55f7fe..ff8576f21e 100644
> --- a/block/ssh.c
> +++ b/block/ssh.c
> @@ -803,17 +803,24 @@ static int ssh_file_open(BlockDriverState *bs, QDict *options, int bdrv_flags,
>       return ret;
>   }
>   
> +/* Note: This is a blocking operation */
>   static int ssh_grow_file(BDRVSSHState *s, int64_t offset, Error **errp)
>   {
>       ssize_t ret;
>       char c[1] = { '\0' };
> +    int was_blocking = libssh2_session_get_blocking(s->session);
>   
>       /* offset must be strictly greater than the current size so we do
>        * not overwrite anything */
>       assert(offset > 0 && offset > s->attrs.filesize);
>   
> +    libssh2_session_set_blocking(s->session, 1);
> +
>       libssh2_sftp_seek64(s->sftp_handle, offset - 1);
>       ret = libssh2_sftp_write(s->sftp_handle, c, 1);
> +
> +    libssh2_session_set_blocking(s->session, was_blocking);

Is it worth skipping the two libssh2_session_set_blocking() calls if 
was_blocking is 1?  But that's a micro-optimization that probably won't 
be noticeable, so I'm also fine with unconditional.

Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-02-14 21:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 20:49 [Qemu-devel] [PATCH 0/3] block/ssh: Add basic .bdrv_truncate() Max Reitz
2018-02-14 20:49 ` [Qemu-devel] [PATCH 1/3] block/ssh: Pull ssh_grow_file() from ssh_create() Max Reitz
2018-02-14 21:08   ` Eric Blake
2018-02-14 20:49 ` [Qemu-devel] [PATCH 2/3] block/ssh: Make ssh_grow_file() blocking Max Reitz
2018-02-14 21:11   ` Eric Blake [this message]
2018-02-14 21:28     ` Max Reitz
2018-02-14 20:49 ` [Qemu-devel] [PATCH 3/3] block/ssh: Add basic .bdrv_truncate() Max Reitz
2018-02-14 21:12   ` Eric Blake
2018-02-15 11:12   ` Richard W.M. Jones
2018-02-23 13:51 ` [Qemu-devel] [PATCH 0/3] " Max Reitz

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=eb2c00e1-eae0-7d71-b4dc-0df0054a3fb2@redhat.com \
    --to=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@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;
as well as URLs for NNTP newsgroup(s).