qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 4/9] qemu-sockets: add error propagation to Unix socket functions
Date: Tue, 02 Oct 2012 08:09:20 +0200	[thread overview]
Message-ID: <k4e0ef$po$1@ger.gmane.org> (raw)
In-Reply-To: <20121001200507.62da4412@doriath.home>

Il 02/10/2012 01:05, Luiz Capitulino ha scritto:
> On Mon, 01 Oct 2012 21:07:52 +0200
> Paolo Bonzini <pbonzini@redhat.com> wrote:
> 
>> Il 01/10/2012 19:17, Luiz Capitulino ha scritto:
>>>>>      if (bind(sock, (struct sockaddr*) &un, sizeof(un)) < 0) {
>>>>> -        fprintf(stderr, "bind(unix:%s): %s\n", un.sun_path, strerror(errno));
>>>>> +        error_set(errp, QERR_SOCKET_BIND_FAILED);
>>> This drops error information, making the error message worse. I believe
>>> you have a reason to not use error_setg()?
>>
>> I was waiting for the end of the discussion on errno to add
>> error_setg_errno.
> 
> The decision was to not add errno now, right?

I don't remember, but we can still add a function that takes an errno
value and tacks on the strerror(errno).

>>> Also, I see that in some hunks you do something like:
>>>
>>>   -            fd = unix_listen_opts(opts);
>>>   +            fd = unix_listen_opts(opts, NULL);
>>>
>>> This will break printing the error message to the user. It's fine by me if
>>> you do this only temporarily (ie. this is fixed by the next or a later patch),
>>> but want to double check that you're aware of it.
>>
>> I want to avoid super-large patch series, so I would prefer to fix it
>> later in the 1.3 development.
> 
> We at least need to have the patches flying, I don't think it's ok to
> break error reporting like that.

I disagree because we still have two months before release, but I'll see
what I can do.

Paolo

  reply	other threads:[~2012-10-02  6:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 14:52 [Qemu-devel] [PATCH v2 0/9] Embedded NBD server Paolo Bonzini
2012-10-01 14:52 ` [Qemu-devel] [PATCH v2 1/9] build: add QAPI files to the tools Paolo Bonzini
2012-10-02 12:31   ` Luiz Capitulino
2012-10-01 14:52 ` [Qemu-devel] [PATCH v2 2/9] qapi: add socket address types Paolo Bonzini
2012-10-01 23:56   ` Eric Blake
2012-10-02  9:00     ` Paolo Bonzini
2012-10-02 11:39       ` Eric Blake
2012-10-02 12:27         ` Luiz Capitulino
2012-10-02 14:24           ` Paolo Bonzini
2012-10-02 15:27             ` Luiz Capitulino
2012-10-02 15:31               ` Paolo Bonzini
2012-10-02 12:32   ` Luiz Capitulino
2012-10-01 14:52 ` [Qemu-devel] [PATCH v2 3/9] qemu-sockets: add error propagation to inet_parse Paolo Bonzini
2012-10-02 12:34   ` Luiz Capitulino
2012-10-01 14:52 ` [Qemu-devel] [PATCH v2 4/9] qemu-sockets: add error propagation to Unix socket functions Paolo Bonzini
2012-10-01 17:17   ` Luiz Capitulino
2012-10-01 19:07     ` Paolo Bonzini
2012-10-01 23:05       ` Luiz Capitulino
2012-10-02  6:09         ` Paolo Bonzini [this message]
2012-10-01 14:52 ` [Qemu-devel] [PATCH v2 5/9] qemu-sockets: return IPSocketAddress from inet_parse Paolo Bonzini
2012-10-02 12:36   ` Luiz Capitulino
2012-10-01 14:52 ` [Qemu-devel] [PATCH v2 6/9] qemu-sockets: add socket_listen, socket_connect, socket_parse Paolo Bonzini
2012-10-02 12:37   ` Luiz Capitulino
2012-10-01 14:52 ` [Qemu-devel] [PATCH v2 7/9] block: add close notifiers Paolo Bonzini
2012-10-01 14:52 ` [Qemu-devel] [PATCH v2 8/9] qmp: add NBD server commands Paolo Bonzini
2012-10-02  2:50   ` Eric Blake
2012-10-02 12:37   ` Luiz Capitulino
2012-10-31 11:23   ` Christoph Hellwig
2012-10-31 12:46     ` Paolo Bonzini
2012-10-31 13:01       ` Christoph Hellwig
2012-10-01 14:52 ` [Qemu-devel] [PATCH v2 9/9] hmp: " Paolo Bonzini
2012-10-02 12:38   ` Luiz Capitulino
2012-10-01 18:08 ` [Qemu-devel] [PATCH v2 0/9] Embedded NBD server Luiz Capitulino

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='k4e0ef$po$1@ger.gmane.org' \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).