From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] qtest: don't leak pid files and UNIX domain sockets
Date: Mon, 3 Feb 2014 11:24:40 +0000 [thread overview]
Message-ID: <CAFEAcA995mkJFqz0xJdrt8-Y1WDdG4U3UXW8N11oPoVdBNEZVA@mail.gmail.com> (raw)
In-Reply-To: <52EF7909.4060601@suse.de>
On 3 February 2014 11:10, Andreas Färber <afaerber@suse.de> wrote:
> As an explanation, the temporary files contain the PID. When they remain
> behind due to test failure *and* the PID wraps around and file names
> thus happen to match, the error was triggered, and thereby not on each
> run but seemingly "sometimes".
Yeah, that's what it looks like to me too.
> I am not 100% familiar with the unlinking and code ordering here, but it
> had looked sane to me back when I looked at it, I just didn't feel
> confident enough for a Reviewed-by. I could give it a spin and add a
> Tested-by if that reassures PMM.
I'm happy the code is good, I'm just being lazy about directly
applying patches to master, especially since Anthony's patches
db is currently stalled and not updating :-) (I guess I need to
deal with that some time, though, since we don't have a mechanism
for handling patches that fall through the cracks between
subsystems beyond "somebody with commit access applies them"...)
thanks
-- PMM
prev parent reply other threads:[~2014-02-03 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 11:03 [Qemu-devel] [PATCH 0/2] qtest: don't leak pid files and UNIX domain sockets Stefan Hajnoczi
2013-11-21 11:03 ` [Qemu-devel] [PATCH 1/2] qtest: unlink QEMU pid file after startup Stefan Hajnoczi
2013-12-06 10:59 ` Markus Armbruster
2013-11-21 11:03 ` [Qemu-devel] [PATCH 2/2] qtest: unlink UNIX domain sockets after connecting Stefan Hajnoczi
2013-12-05 15:57 ` [Qemu-devel] [PATCH 0/2] qtest: don't leak pid files and UNIX domain sockets Stefan Hajnoczi
2013-12-06 11:07 ` Markus Armbruster
2014-01-31 0:07 ` Peter Maydell
2014-01-31 10:56 ` Stefan Hajnoczi
2014-02-03 9:00 ` Gerd Hoffmann
2014-02-03 9:54 ` Stefan Hajnoczi
2014-02-03 10:30 ` Peter Maydell
2014-02-03 15:22 ` Stefan Hajnoczi
2014-02-03 11:10 ` Andreas Färber
2014-02-03 11:24 ` Peter Maydell [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=CAFEAcA995mkJFqz0xJdrt8-Y1WDdG4U3UXW8N11oPoVdBNEZVA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=kraxel@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 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).