From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12207 invoked by alias); 25 Jul 2019 17:32:14 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 12196 invoked by uid 89); 25 Jul 2019 17:32:14 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=Howard, howard, H*UA:Win32, killing X-HELO: zmcc-2-mx.zmailcloud.com Received: from zmcc-2-mx.zmailcloud.com (HELO zmcc-2-mx.zmailcloud.com) (52.37.197.7) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 25 Jul 2019 17:32:13 +0000 Received: from zmcc-2.zmailcloud.com (zmcc-2-mta-1.zmailcloud.com [146.148.52.56]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by zmcc-2-mx.zmailcloud.com (Postfix) with ESMTPS id 96EAE4058D for ; Thu, 25 Jul 2019 13:47:54 -0400 (EDT) Received: from zmcc-2.zmailcloud.com (localhost [127.0.0.1]) by zmcc-2-mta-1.zmailcloud.com (Postfix) with ESMTPS id 8E636CE2AC for ; Thu, 25 Jul 2019 12:32:10 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by zmcc-2-mta-1.zmailcloud.com (Postfix) with ESMTP id 81DBECE29E for ; Thu, 25 Jul 2019 12:32:10 -0500 (CDT) Received: from zmcc-2.zmailcloud.com ([127.0.0.1]) by localhost (zmcc-2-mta-1.zmailcloud.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id sKTEIXeQ4vlr for ; Thu, 25 Jul 2019 12:32:10 -0500 (CDT) Received: from [192.168.1.39] (47-208-128-44.erkacmtk03.res.dyn.suddenlink.net [47.208.128.44]) by zmcc-2-mta-1.zmailcloud.com (Postfix) with ESMTPSA id 4EAF3CE29C for ; Thu, 25 Jul 2019 12:32:10 -0500 (CDT) Date: Thu, 25 Jul 2019 17:32:00 -0000 From: Quanah Gibson-Mount Reply-To: Quanah Gibson-Mount To: cygwin@cygwin.com Subject: Bug report: Killing a native process may not actually kill it Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-IsSubscribed: yes X-SW-Source: 2019-07/txt/msg00221.txt.bz2 As found and reported to the MSYS team back in 2006 by Howard Chu, if a native process is spawned, control-C, the kill command, etc, may not actually kill the process. Details are here: as well as here: Given that there is now 64-bit windows, the issue would be a bit more complex to resolve, as an updated patch would need to query first to see if the target process is 32-bit or 64-bit, and then a 64-bit version of the patch needs to be created. The inability to properly kill such a spawned process can lead to things like the dreaded "Device or resource busy" error, since the process that is using the related file has actually never terminated. It's fairly trivial to reproduce this in the OpenLDAP test suite, particularly test001, which spawns a slapd process, kills it, then spawns another slapd process, which will fail because the original slapd never actually got killed. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple