From: Michal Privoznik <mprivozn@redhat.com>
To: John Ferlan <jferlan@redhat.com>, Jim Fehlig <jfehlig@suse.com>,
libvir-list@redhat.com
Cc: ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: [libvirt] [PATCH V2] libxl: don't overwrite error from virNetSocketNewConnectTCP()
Date: Fri, 4 Sep 2015 10:21:59 +0200 [thread overview]
Message-ID: <55E954A7.8080004@redhat.com> (raw)
In-Reply-To: <55E8B3DF.4040605@redhat.com>
On 03.09.2015 22:55, John Ferlan wrote:
>
>
> On 09/03/2015 01:40 PM, Jim Fehlig wrote:
>> Remove redundant error reporting in libxlDomainMigrationPerform().
>> virNetSocketNewConnectTCP() is perfectly capable of reporting
>> sensible errors.
>>
>> Signed-off-by: Jim Fehlig <jfehlig@suse.com>
>> ---
>>
>> V2:
>> Actually try to compile the code and find saved_errno is no
>> longer used - remove it.
>>
>> src/libxl/libxl_migration.c | 7 +------
>> 1 file changed, 1 insertion(+), 6 deletions(-)
>>
>
> ACK
>
> John
>
> Also noteworthy that virNetSocketNewConnectTCP could overwrite errno
> when freeaddrinfo is run in error: or when VIR_FORCE_CLOSE() did it's
> thing...
>
I don't think that either of those overwrites errno. Here's
freeaddrinfo() impl that I've found in glibc:
void
freeaddrinfo (struct addrinfo *ai)
{
struct addrinfo *p;
while (ai != NULL)
{
p = ai;
ai = ai->ai_next;
free (p->ai_canonname);
free (p);
}
}
And VIR_FORCE_CLOSE() preserves errno too. But nevertheless, ACK stands.
Michal
prev parent reply other threads:[~2015-09-04 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1441302033-20508-1-git-send-email-jfehlig@suse.com>
2015-09-03 20:55 ` [libvirt] [PATCH V2] libxl: don't overwrite error from virNetSocketNewConnectTCP() John Ferlan
[not found] ` <55E8B3DF.4040605@redhat.com>
2015-09-04 2:44 ` Jim Fehlig
2015-09-04 8:21 ` Michal Privoznik [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=55E954A7.8080004@redhat.com \
--to=mprivozn@redhat.com \
--cc=ian.campbell@citrix.com \
--cc=jfehlig@suse.com \
--cc=jferlan@redhat.com \
--cc=libvir-list@redhat.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.