From: czylin@uwaterloo.ca
To: Ian Campbell <ian.campbell@citrix.com>
Cc: wei.liu2@citrix.com, stefano.stabellini@eu.citrix.com,
dario.faggioli@citrix.com, ian.jackson@eu.citrix.com,
xen-devel@lists.xen.org, jtotto@uwaterloo.ca,
hjarmstr@uwaterloo.ca
Subject: Re: [PATCH v3 2/5] libxl: make GC_FREE reachable in libxl_get_scheduler()
Date: Mon, 01 Feb 2016 23:39:47 -0500 [thread overview]
Message-ID: <20160201233947.134335gv8q8by0pf@www.nexusmail.uwaterloo.ca> (raw)
In-Reply-To: <1453827169.25257.45.camel@citrix.com>
Quoting Ian Campbell <ian.campbell@citrix.com>:
> On Mon, 2016-01-25 at 11:59 +0000, Ian Campbell wrote:
>> On Sun, 2016-01-24 at 19:45 -0500, Chester Lin wrote:
>> > Coverity CID 1343309
>> >
>> > Make GC_FREE reachable in all cases in libxl_get_scheduler() by
>> > eliminating the error-path return and instead storing the error code in
>> > the returned variable.
>> >
>> > To make this semantically consistent, change the return type of
>> > libxl_get_scheduler() from libxl_scheduler to int, and make a note of
>> > the interpretation of the return value in libxl.h. N.B. This change
>> > does not change the API in a way that affects functionality.
>> >
>> > The libxl_scheduler enum is consistent with the sched_id return value
>> > of xc_sched_id and this must continue to be true.
>> >
>> > Suggested-by: Ian Campbell <ian.campbell@citrix.com>
>> > Signed-off-by: Chester Lin <czylin@uwaterloo.ca>
>> > Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
>>
>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>
> Applied.
>
>> I can't see any sign of v3 versions of #3, #4 or #5/5 in my INBOX, have
>> they gone astray?
>>
>> Also, both #1 and #2 seem to have been sent independently using separate
>> git send-email invocations. Please send them from one single invocation, as
>> reply to a cover letter (which may be referenced with --in-reply-to, or
>> written using --compose) such that they are all properly threaded together
>> into a message thread.
>
> I've retired the previous #3..#5 out of my queue (without applying
> anything) in anticipation of a resend iff they are still needed.
>
> Ian.
>
>
I'm sorry for any confusion. I didn't send patch #3 because I thought
there was agreement that it would be better to disable the check in
the tool than make any code changes.
We also do not intend to follow up with the IDL refactoring as per
your earlier comments. If you would like us to resend any of the
patches for further debate or archiving, I will.
On behalf of Josh, Harley, and myself, I'd like to thank the
maintainers for reviewing our patches.
prev parent reply other threads:[~2016-02-02 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 0:45 [PATCH v3 2/5] libxl: make GC_FREE reachable in libxl_get_scheduler() Chester Lin
2016-01-25 11:59 ` Ian Campbell
2016-01-26 16:52 ` Ian Campbell
2016-02-02 4:39 ` czylin [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=20160201233947.134335gv8q8by0pf@www.nexusmail.uwaterloo.ca \
--to=czylin@uwaterloo.ca \
--cc=dario.faggioli@citrix.com \
--cc=hjarmstr@uwaterloo.ca \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jtotto@uwaterloo.ca \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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 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).