From: Stefan Weil <sw@weilnetz.de>
To: Sebastian Ottlik <ottlik@fzi.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] [PATCH v5 0/5] Do not set SO_REUSEADDR on Windows
Date: Tue, 01 Oct 2013 18:44:11 +0200 [thread overview]
Message-ID: <524AFBDB.7010206@weilnetz.de> (raw)
In-Reply-To: <524A83A8.3020909@fzi.de>
Am 01.10.2013 10:11, schrieb Sebastian Ottlik:
> On 23.09.2013 12:33, Sebastian Ottlik wrote:
>> On 18.09.2013 18:58, Stefan Weil wrote:
>>> If failures only happen when something is very wrong (like an invalid
>>> socket id),
>>> an assertion might be better, and we could remove the 'silent'
>>> parameter.
>>>
>>> Stefan
>>>
>> IMO for debug builds this is a good idea. However, in production use
>> it is probably preferable to keep QEMU running, as a failure won't be
>> too critical. From a quick grep it looks like NDEBUG is not set so
>> assertions wont be removed for non-debug builds. I don't feel
>> acquainted enough with the source code to decide about this kind of
>> change in functionality, which is why I was waiting so long to reply.
> ping
Running QEMU with an invalid socket id is not preferable.
It's better to get a dozen of assertions in production and fix the code
than to have hundreds of production systems running with hidden bugs.
Those users who don't agree can build QEMU with -DNDEBUG and use the
close-your-eyes strategy "if error then no error".
Therefore I strongly suggest adding an assertion and removing the
'silent' parameter.
Regards,
Stefan
next prev parent reply other threads:[~2013-10-01 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 14:23 [Qemu-devel] [PATCH v5 0/5] Do not set SO_REUSEADDR on Windows Sebastian Ottlik
2013-09-16 14:23 ` [Qemu-devel] [PATCH v5 1/5] util: add socket_set_fast_reuse function which will replace setting SO_REUSEADDR Sebastian Ottlik
2013-09-16 14:23 ` [Qemu-devel] [PATCH v5 2/5] gdbstub: call socket_set_fast_reuse instead of " Sebastian Ottlik
2013-09-16 14:23 ` [Qemu-devel] [PATCH v5 3/5] net: " Sebastian Ottlik
2013-09-16 14:23 ` [Qemu-devel] [PATCH v5 4/5] slirp: " Sebastian Ottlik
2013-09-16 14:23 ` [Qemu-devel] [PATCH v5 5/5] util: " Sebastian Ottlik
2013-09-16 14:55 ` [Qemu-devel] [PATCH v5 0/5] Do not set SO_REUSEADDR on Windows Paolo Bonzini
2013-09-16 15:10 ` Sebastian Ottlik
2013-09-18 16:58 ` Stefan Weil
2013-09-23 10:33 ` Sebastian Ottlik
2013-10-01 8:11 ` Sebastian Ottlik
2013-10-01 16:44 ` Stefan Weil [this message]
2013-09-18 12:42 ` Stefan Hajnoczi
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=524AFBDB.7010206@weilnetz.de \
--to=sw@weilnetz.de \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=ottlik@fzi.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.