From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v2] Don't leak file descriptors
Date: Wed, 02 Dec 2009 08:04:16 -0600 [thread overview]
Message-ID: <4B1673E0.1030301@codemonkey.ws> (raw)
In-Reply-To: <4B164EF7.4070201@redhat.com>
Kevin Wolf wrote:
> Am 02.12.2009 12:24, schrieb Kevin Wolf:
>
>> We're leaking file descriptors to child processes. Set FD_CLOEXEC on file
>> descriptors that don't need to be passed to children to stop this misbehaviour.
>>
>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
>> ---
>>
>> v2:
>> - The existence of SOCK_CLOEXEC doesn't mean that accept4 exists. Added a check
>> for it in configure.
>>
>
> v3 even. Anthony, I hope this doesn't confuse your scripts?
>
No worries, I'll straighten it out.
> Kevin
>
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-12-02 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 11:24 [Qemu-devel] [PATCH v2] Don't leak file descriptors Kevin Wolf
2009-12-02 11:26 ` [Qemu-devel] " Kevin Wolf
2009-12-02 12:03 ` Scott Tsai
2009-12-02 12:58 ` Kevin Wolf
2009-12-02 14:04 ` Anthony Liguori [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=4B1673E0.1030301@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kwolf@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).