From: Stefan Hajnoczi <stefanha@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@amazon.com>,
Andreas Faerber <afaerber@suse.de>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] qtest: kill QEMU process on g_assert() failure
Date: Tue, 18 Feb 2014 15:44:23 +0100 [thread overview]
Message-ID: <20140218144423.GC15348@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <87zjloiw2b.fsf@blackfin.pond.sub.org>
On Tue, Feb 18, 2014 at 10:55:56AM +0100, Markus Armbruster wrote:
> Stefan Hajnoczi <stefanha@gmail.com> writes:
>
> > On Mon, Feb 17, 2014 at 05:49:31PM +0100, Markus Armbruster wrote:
> >> Stefan Hajnoczi <stefanha@redhat.com> writes:
> >> > if (s->qemu_pid != -1) {
> >> > kill(s->qemu_pid, SIGTERM);
> >> > waitpid(s->qemu_pid, &status, 0);
> >> > }
> >> >
> >> > - close(s->fd);
> >> > - close(s->qmp_fd);
> >> > + if (s->fd != -1) {
> >> > + close(s->fd);
> >> > + }
> >> > + if (s->qmp_fd != -1) {
> >> > + close(s->qmp_fd);
> >> > + }
> >>
> >> I generally don't bother to avoid close(-1).
> >
> > When I drive on the highway I stay on the lanes but I guess I could just
> > slide along the side barriers :). It's a style issue but close(-1)
> > annoys me in strace so I try to avoid doing it.
>
> For me, it's in the same category as free(NULL).
Understood. I'll drop it from the next patch.
next prev parent reply other threads:[~2014-02-18 14:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 15:44 [Qemu-devel] [PATCH 0/3] qtest: avoid pidfile and QEMU process leaks Stefan Hajnoczi
2014-02-17 15:44 ` [Qemu-devel] [PATCH 1/3] qtest: drop unused child_pid field Stefan Hajnoczi
2014-02-17 15:44 ` [Qemu-devel] [PATCH 2/3] qtest: make QEMU our direct child process Stefan Hajnoczi
2014-02-17 16:44 ` Markus Armbruster
2014-02-18 9:00 ` Stefan Hajnoczi
2014-02-18 9:53 ` Markus Armbruster
2014-02-17 15:44 ` [Qemu-devel] [PATCH 3/3] qtest: kill QEMU process on g_assert() failure Stefan Hajnoczi
2014-02-17 16:16 ` Paolo Bonzini
2014-02-17 17:00 ` Markus Armbruster
2014-02-18 9:05 ` Stefan Hajnoczi
2014-02-18 10:05 ` Markus Armbruster
2014-02-18 10:23 ` Paolo Bonzini
2014-02-18 10:43 ` Markus Armbruster
2014-02-18 14:38 ` Stefan Hajnoczi
2014-02-18 10:07 ` Paolo Bonzini
2014-02-18 10:17 ` Daniel P. Berrange
2014-02-18 10:23 ` Paolo Bonzini
2014-02-17 16:49 ` Markus Armbruster
2014-02-17 16:56 ` Paolo Bonzini
2014-02-18 9:17 ` Stefan Hajnoczi
2014-02-18 9:55 ` Markus Armbruster
2014-02-18 14:44 ` Stefan Hajnoczi [this message]
2014-02-18 14:56 ` Peter Maydell
2014-02-18 10:02 ` Markus Armbruster
2014-02-18 14:38 ` Stefan Hajnoczi
2014-02-18 14:52 ` Markus Armbruster
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=20140218144423.GC15348@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).