From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NFnvW-00033K-L9
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 07:03:22 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NFnvR-0002zJ-V2
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 07:03:22 -0500
Received: from [199.232.76.173] (port=48620 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NFnvR-0002z7-Nd
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 07:03:17 -0500
Received: from mail-pw0-f43.google.com ([209.85.160.43]:34848)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <scottt.tw@gmail.com>) id 1NFnvR-00042z-AS
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 07:03:17 -0500
Received: by pwi12 with SMTP id 12so74875pwi.2
	for <qemu-devel@nongnu.org>; Wed, 02 Dec 2009 04:03:15 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <4B164EF7.4070201@redhat.com>
References: <1259753082-24840-1-git-send-email-kwolf@redhat.com>
	<4B164EF7.4070201@redhat.com>
Date: Wed, 2 Dec 2009 20:03:15 +0800
Message-ID: <ef2f888d0912020403w121542bbkf795a8376064cb12@mail.gmail.com>
Subject: Re: [Qemu-devel] Re: [PATCH v2] Don't leak file descriptors
From: Scott Tsai <scottt.tw@gmail.com>
Content-Type: text/plain; charset=UTF-8
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org

On Wed, Dec 2, 2009 at 7:26 PM, Kevin Wolf <kwolf@redhat.com> wrote:
> v3 even. Anthony, I hope this doesn't confuse your scripts?

Kevin, I see use of fopen, fdopen, popen, eventfd in qemu without the
equivalent of CLOEXEC set.
Do you want to handle those in this patch series as well?