From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Roger Pau Monne <roger.pau@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Patch v3 3/4] tools/libxl: Fix libxl__device_nic_from_xs_be()
Date: Tue, 26 Nov 2013 11:42:35 +0000 [thread overview]
Message-ID: <5294892B.5030003@citrix.com> (raw)
In-Reply-To: <21140.34516.685325.920576@mariner.uk.xensource.com>
On 26/11/13 11:32, Ian Jackson wrote:
> Andrew Cooper writes ("[Xen-devel] [Patch v3 3/4] tools/libxl: Fix libxl__device_nic_from_xs_be()"):
>> diff --git a/tools/libxl/libxl.c b/tools/libxl/libxl.c
>> - tmp = xs_read(ctx->xsh, XBT_NULL,
>> - libxl__sprintf(gc, "%s/handle", be_path), &len);
>> - if ( tmp )
>> + rc = libxl__xs_read_checked(gc, XBT_NULL,
>> + libxl__sprintf(gc, "%s/handle", be_path),
>> + &tmp);
>> +
>> + if ((rc == 0) && strlen(tmp))
> Nacked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> (for the benefit of Ian C.)
>
> This is not correct. See the doc comment for libxl__xs_read_checked:
>
> /* On success, *result_out came from the gc.
> * On error, *result_out is undefined.
> * ENOENT counts as success but sets *result_out=0
> */
> int libxl__xs_read_checked(libxl__gc *gc, xs_transaction_t t,
> const char *path, const char **result_out);
>
> So the correct pattern is:
>
> rc = libxl__xs_read_checked(gc, XBT_NULL, blah blah blah, &tmp);
> if (rc) goto out;
>
> if (tmp) {
> use tmp;
> } else {
> the path doesn't exist, do the other thing;
> }
>
> I don't think there should be any need to check for empty strings
> written to xenstore here ? The old code doesn't. Please someone tell
> me there isn't.
>
> Thanks,
> Ian.
Ah - I think I have gotten the wrong indirection on tmp when attempting
to apply the documented ENOENT behaviour.
As this function cant fail, I was trying to force all error paths to
apply safe defaults to the libxl_device_nic structure.
I believe substituting the strlen(tmp) check for NULL checks will
produce the intended behaviour?
~Andrew
next prev parent reply other threads:[~2013-11-26 11:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 11:12 [PATCH 0/4] Coverity fixes for tools/libxl Andrew Cooper
2013-11-25 11:12 ` [PATCH 1/4] tools/libxl: Avoid deliberate NULL pointer dereference Andrew Cooper
2013-11-25 12:32 ` Ian Jackson
2013-11-25 11:12 ` [PATCH 2/4] tools/libxl: Fix integer overflows in sched_sedf_domain_set() Andrew Cooper
2013-11-25 12:35 ` Ian Jackson
2013-11-25 11:12 ` [PATCH 3/4] tools/libxl: Fix libxl__device_nic_from_xs_be() Andrew Cooper
2013-11-25 11:38 ` Roger Pau Monné
2013-11-25 15:19 ` [Patch v2 " Andrew Cooper
2013-11-25 18:52 ` Roger Pau Monné
2013-11-25 20:49 ` [Patch v3 " Andrew Cooper
2013-11-26 8:11 ` Roger Pau Monné
2013-11-26 11:32 ` Ian Jackson
2013-11-26 11:42 ` Andrew Cooper [this message]
2013-11-26 12:09 ` Ian Jackson
2013-11-26 13:58 ` Andrew Cooper
2013-11-26 15:08 ` Ian Jackson
2013-11-26 15:15 ` Andrew Cooper
2013-11-26 15:39 ` Ian Jackson
2013-12-09 13:35 ` Andrew Cooper
2013-12-18 11:11 ` Ian Campbell
2013-12-18 11:10 ` Ian Campbell
2013-11-25 12:38 ` [PATCH " Ian Jackson
2013-11-25 11:12 ` [PATCH 4/4] tools/libxl: Fix memory leak in sched_domain_output() Andrew Cooper
2013-11-25 13:46 ` Ian Jackson
2013-11-25 13:48 ` Andrew Cooper
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=5294892B.5030003@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.