From: Eric Blake <eblake@redhat.com>
To: Jeff Cody <jcody@redhat.com>, qemu-devel@nongnu.org
Cc: mitake.hitoshi@lab.ntt.co.jp, namei.unix@gmail.com,
kwolf@redhat.com, rjones@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/7] block/ssh: don't call libssh2_init() in block_init()
Date: Wed, 30 Aug 2017 14:40:16 -0500 [thread overview]
Message-ID: <94eb9a23-1cb7-a139-039e-4d0f138a6244@redhat.com> (raw)
In-Reply-To: <af4268153bce149a9599e4079a0f8908e32fdef8.1504112061.git.jcody@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
On 08/30/2017 11:56 AM, Jeff Cody wrote:
> We don't need libssh2 failure to be fatal (we could just opt to not
> register the driver on failure). But, it is probably a good idea to
> avoid external library calls during the block_init(), and call the
> libssh2 global init function on the first usage, returning any errors.
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
> block/ssh.c | 40 +++++++++++++++++++++++++++++-----------
> 1 file changed, 29 insertions(+), 11 deletions(-)
>
> +static int ssh_state_init(BDRVSSHState *s, Error **errp)
> {
> + int ret;
> +
> + if (!ssh_libinit_called) {
> + ret = libssh2_init(0);
> + if (ret) {
> + error_setg(errp, "libssh2 initialization failed with %d", ret);
> + return ret;
Do we know if this number is always positive or negative?
> @@ -772,8 +788,13 @@ static int ssh_file_open(BlockDriverState *bs, QDict *options, int bdrv_flags,
> BDRVSSHState *s = bs->opaque;
> int ret;
> int ssh_flags;
> + Error *local_err = NULL;
>
> - ssh_state_init(s);
> + ret = ssh_state_init(s, &local_err);
> + if (local_err) {
> + error_propagate(errp, local_err);
> + return ret;
Is returning 'ret' from libssh2_init() wise?
If 'ret' is not important, you could simplify this:
if (ssh_state_init(s, errp)) {
return -1;
}
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-30 19:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 16:56 [Qemu-devel] [PATCH v2 0/7] Code cleanup and minor fixes Jeff Cody
2017-08-30 16:56 ` [Qemu-devel] [PATCH v2 1/7] block/ssh: don't call libssh2_init() in block_init() Jeff Cody
2017-08-30 19:40 ` Eric Blake [this message]
2017-08-30 20:11 ` Jeff Cody
2017-08-30 20:12 ` Eric Blake
2017-08-31 7:46 ` Richard W.M. Jones
2017-08-30 16:56 ` [Qemu-devel] [PATCH v2 2/7] block/ssh: make compliant with coding guidelines Jeff Cody
2017-08-30 19:41 ` Eric Blake
2017-08-30 16:57 ` [Qemu-devel] [PATCH v2 3/7] block/sheepdog: remove spurious NULL check Jeff Cody
2017-08-30 17:37 ` Philippe Mathieu-Daudé
2017-08-30 19:42 ` Eric Blake
2017-08-30 16:57 ` [Qemu-devel] [PATCH v2 4/7] block/sheepdog: code beautification Jeff Cody
2017-08-30 19:48 ` Eric Blake
2017-08-30 16:57 ` [Qemu-devel] [PATCH v2 5/7] block/curl: check error return of curl_global_init() Jeff Cody
2017-08-30 19:49 ` Eric Blake
2017-08-30 16:57 ` [Qemu-devel] [PATCH v2 6/7] block/curl: fix minor memory leaks Jeff Cody
2017-08-30 19:51 ` Eric Blake
2017-08-30 16:57 ` [Qemu-devel] [PATCH v2 7/7] block/curl: code cleanup to comply with coding style Jeff Cody
2017-08-30 19:53 ` Eric Blake
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=94eb9a23-1cb7-a139-039e-4d0f138a6244@redhat.com \
--to=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=namei.unix@gmail.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).