From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PULL 0/2] qtest: don't leak pid files and UNIX domain sockets
Date: Sun, 09 Feb 2014 12:40:01 +0100 [thread overview]
Message-ID: <52F76911.1030808@suse.de> (raw)
In-Reply-To: <CAFEAcA-2XoKAJT+hS+bg3OX_AfgnTc1Va=c-0gOiNesnXdYONQ@mail.gmail.com>
Am 07.02.2014 17:41, schrieb Peter Maydell:
> On 4 February 2014 08:31, Stefan Hajnoczi <stefanha@redhat.com> wrote:
>> On Mon, Feb 03, 2014 at 04:01:00PM +0000, Peter Maydell wrote:
>>> On 3 February 2014 15:20, Stefan Hajnoczi <stefanha@redhat.com> wrote:
>>>> This pull request has been rebased onto qemu.git/master and retested.
>>>>
>>>> The series fixes init_socket() failures when reused PIDs cause temporary file
>>>> name collisions.
>>>
>>> Your pull request appears to be missing the critically
>>> important part, ie the git repo/branch/tag information
>>> to pull from... ("git request-pull" is your friend here.)
>>
>> Oops, I ran the wrong script. Here are the full details and signed tag:
>
> Applied, thanks.
Thanks. I've stumbled over a remaining pid file leak:
http://patchwork.ozlabs.org/patch/318576/
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2014-02-09 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 15:20 [Qemu-devel] [PULL 0/2] qtest: don't leak pid files and UNIX domain sockets Stefan Hajnoczi
2014-02-03 15:20 ` [Qemu-devel] [PULL 1/2] qtest: unlink QEMU pid file after startup Stefan Hajnoczi
2014-02-03 15:20 ` [Qemu-devel] [PULL 2/2] qtest: unlink UNIX domain sockets after connecting Stefan Hajnoczi
2014-02-03 16:01 ` [Qemu-devel] [PULL 0/2] qtest: don't leak pid files and UNIX domain sockets Peter Maydell
2014-02-04 8:31 ` Stefan Hajnoczi
2014-02-07 16:41 ` Peter Maydell
2014-02-09 11:40 ` Andreas Färber [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=52F76911.1030808@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.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).