From: Dario Faggioli <dario.faggioli@citrix.com>
To: Harmandeep Kaur <write.harmandeep@gmail.com>,
xen-devel@lists.xenproject.org
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v3] libxl: fix handling of returns in libxl_get_version_info()
Date: Mon, 15 Feb 2016 11:07:21 +0100 [thread overview]
Message-ID: <1455530841.14334.38.camel@citrix.com> (raw)
In-Reply-To: <1455309313-5149-1-git-send-email-write.harmandeep@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3854 bytes --]
Hey, Harmandeep,
We're almost there, I would say.
The subject is still suboptimal, IMO. I would go for something like
"libxl: handle failure of xc_version() in libxl_get_version_info()
The changelog...
On Sat, 2016-02-13 at 02:05 +0530, Harmandeep Kaur wrote:
> Check the return value of xc_version() and return NULL if it
> fails. libxl_get_version_info() can also return NULL now.
>
Put a blank line here.
> Callers of the function libxl_get_version_info() are already
> prepared to deal with returning NULL on failure of xc_version().
>
Callers don't know what actually failed inside the function, and that
is perfectly ok. I'd just say "are already prepared to deal with a NULL
return value"
> Group all calls to xc_version() , so that data copies in various
> info fields only if all calls to xc_version go error-free.
>
This is not super-important to have here in the changelog. I would have
put it in the "v2:" section, below the "---".
I don't mind too much if you want to leave it here, though.
> diff --git a/tools/libxl/libxl.c b/tools/libxl/libxl.c
> index 2d18b8d..f660280 100644
> --- a/tools/libxl/libxl.c
> +++ b/tools/libxl/libxl.c
> @@ -5267,42 +5267,44 @@ const libxl_version_info*
> libxl_get_version_info(libxl_ctx *ctx)
> xen_platform_parameters_t p_parms;
> xen_commandline_t xen_commandline;
> } u;
> - long xen_version;
> + long r = 0;
> libxl_version_info *info = &ctx->version_info;
>
> if (info->xen_version_extra != NULL)
> goto out;
>
> - xen_version = xc_version(ctx->xch, XENVER_version, NULL);
> - info->xen_version_major = xen_version >> 16;
> - info->xen_version_minor = xen_version & 0xFF;
> -
> - xc_version(ctx->xch, XENVER_extraversion, &u.xen_extra);
> + r = xc_version(ctx->xch, XENVER_version, NULL);
> + if (r < 0) goto out;
> + r = xc_version(ctx->xch, XENVER_extraversion, &u.xen_extra);
> + if (r < 0) goto out;
> + r = xc_version(ctx->xch, XENVER_compile_info, &u.xen_cc);
> + if (r < 0) goto out;
> + r = xc_version(ctx->xch, XENVER_capabilities, &u.xen_caps);
> + if (r < 0) goto out;
> + r = xc_version(ctx->xch, XENVER_changeset, &u.xen_chgset);
> + if (r < 0) goto out;
> + r = xc_version(ctx->xch, XENVER_platform_parameters,
> &u.p_parms);
> + if (r < 0) goto out;
> + r = info->pagesize = xc_version(ctx->xch, XENVER_pagesize,
> NULL);
> + if (r < 0) goto out;
> + r = xc_version(ctx->xch, XENVER_commandline,
> &u.xen_commandline);
> + if (r < 0) goto out;
> +
> + info->xen_version_major = r >> 16;
> + info->xen_version_minor = r & 0xFF;
>
But now you are using the value of 'r' returned by
xc_version(ctx->xch, XENVER_commandline, &u.xen_commandline),
which is not what you want!
You either need to make the call to
xc_version(ctx->xch, XENVER_version, NULL) the last one, or avoid
getting rid of the xen_version local variable.
I'd do the latter. I know it was me that suggested you did not need it,
but that was with the previous structure of the function. With this re-
arrangement, I think it's more than fine to keep it.
But that's mostly a matter of taste (yours, and tools' maintainers' one
:-D).
> out:
> GC_FREE;
> - return info;
> + return r < 0 ? NULL:info;
>
NULL : info; (spaces around ':').
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-02-15 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 20:35 [PATCH v3] libxl: fix handling of returns in libxl_get_version_info() Harmandeep Kaur
2016-02-15 10:07 ` Dario Faggioli [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=1455530841.14334.38.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=write.harmandeep@gmail.com \
--cc=xen-devel@lists.xenproject.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).