From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Xen Coverity Team <coverity@xen.org>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.5 1/3] python/xc: Fix multiple issues in pyflask_context_to_sid()
Date: Tue, 9 Dec 2014 11:20:48 -0500 [thread overview]
Message-ID: <20141209162048.GB9585@laptop.dumpdata.com> (raw)
In-Reply-To: <54870780.7040801@citrix.com>
On Tue, Dec 09, 2014 at 02:30:24PM +0000, Andrew Cooper wrote:
> On 09/12/14 14:27, Ian Campbell wrote:
> > On Fri, 2014-11-28 at 11:37 +0000, Ian Campbell wrote:
> >> On Thu, 2014-11-27 at 12:34 +0000, Andrew Cooper wrote:
> >>> The error handling from a failed memory allocation should return
> >>> PyErr_SetFromErrno(xc_error_obj); rather than simply calling it and continuing
> >>> to the memcpy() below, with the dest pointer being NULL.
> >>>
> >>> Furthermore, the context string is simply an input parameter to the hypercall,
> >>> and is not mutated anywhere along the way. The error handling elsewhere in
> >>> the function can be simplified by not duplicating it to start with.
> >>>
> >>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> >>> Coverity-IDs: 1055305 1055721
> >>> CC: Ian Campbell <Ian.Campbell@citrix.com>
> >>> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
> >>> CC: Wei Liu <wei.liu2@citrix.com>
> >>> CC: Xen Coverity Team <coverity@xen.org>
> >> Acked-by: Ian Campbell <ian.campbell@citrix.com>
> >>
> >> This would have been far more obviously correct for 4.5 if you had stuck
> >> to fixing the issue in the first paragraph.
> > Konrad, given
> > http://article.gmane.org/gmane.comp.emulators.xen.devel/224881 does this
> > have a release ack?
> >
> > Ian.
> >
>
> I can resubmit with a clearer description if that would help clarity,
> but the code is correct for the fixes (not fantastically well) described.
Please do - that is all I was waiting for. Thank you.
>
> ~Andrew
next prev parent reply other threads:[~2014-12-09 16:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 12:34 [PATCH for-4.5 0/3] Coverity fixes for python lowlevel libraries Andrew Cooper
2014-11-27 12:34 ` [PATCH for-4.5 1/3] python/xc: Fix multiple issues in pyflask_context_to_sid() Andrew Cooper
2014-11-28 11:37 ` Ian Campbell
2014-11-28 11:47 ` Andrew Cooper
2014-11-28 12:15 ` Ian Campbell
2014-12-09 14:27 ` Ian Campbell
2014-12-09 14:30 ` Andrew Cooper
2014-12-09 16:20 ` Konrad Rzeszutek Wilk [this message]
2014-12-09 16:43 ` [PATCH v2 " Andrew Cooper
2014-12-10 17:13 ` Konrad Rzeszutek Wilk
2014-12-16 17:16 ` Ian Campbell
2014-11-27 12:34 ` [PATCH for-4.5 2/3] python/xc: Fix multiple issues in pyxc_readconsolering() Andrew Cooper
2014-11-28 11:38 ` Ian Campbell
2014-12-01 21:14 ` Konrad Rzeszutek Wilk
2014-12-02 13:50 ` Ian Campbell
2014-12-02 18:47 ` Konrad Rzeszutek Wilk
2014-12-04 13:26 ` Ian Campbell
2014-11-27 12:34 ` [PATCH for-4.5 3/3] python/xs: Correct the indirection of the NULL xshandle() check Andrew Cooper
2014-11-28 11:32 ` Ian Campbell
2014-12-01 21:14 ` Konrad Rzeszutek Wilk
2014-11-28 12:07 ` [PATCH for-4.5 0/3] Coverity fixes for python lowlevel libraries Ian Campbell
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=20141209162048.GB9585@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=coverity@xen.org \
--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 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.