From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-04.nifty.com (conssluserg-04.nifty.com [210.131.2.83]) by sourceware.org (Postfix) with ESMTPS id 694123858D28 for ; Fri, 12 Nov 2021 08:33:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 694123858D28 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=nifty.ne.jp Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=nifty.ne.jp Received: from Express5800-S70 (z221123.dynamic.ppp.asahi-net.or.jp [110.4.221.123]) (authenticated) by conssluserg-04.nifty.com with ESMTP id 1AC8XQeC012855 for ; Fri, 12 Nov 2021 17:33:26 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-04.nifty.com 1AC8XQeC012855 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1636706006; bh=ChRzyUmU50ptYjz2gMiQkbzJO1PyxyuPjUUzTbegd9s=; h=Date:From:To:Subject:In-Reply-To:References:From; b=RIud1u03hBRzXsRWxCR5JklaqTPajSVlfJoxSv19JgIc0MdVuo3+FLPX2FcJsPoR8 1rmHtpSSOsyfzzGOuf2DNlHaOcG/xwXG2SVN8TTeRF7bjdtgX49Dk/4+xaJrcI6nZb aC5UGR0auTHapL1IZXS4F2ADIC+1bAzP7gtqTePUokMTGVBBJQEXF4rkKlaiO6+kQC NCyP+YRRK342EgKn+s+PvGGucErpRy2+YnjJ+6meTEsRxK+t8OUDBLLkOlq63RZfah a2JPeoV9uXFrRufK5Qtqrd30M6mZyM0E9PpTVcgJ8rAnp+D/rgPgcyE4mbvxt98sSY vSFKmvCR8RgHA== X-Nifty-SrcIP: [110.4.221.123] Date: Fri, 12 Nov 2021 17:33:26 +0900 From: Takashi Yano To: cygwin-developers@cygwin.com Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot Message-Id: <20211112173326.71a3a40fececc8a284238051@nifty.ne.jp> In-Reply-To: <20211111201206.72cd688ce6a0d72d3a4f6c5f@nifty.ne.jp> References: <20211105170542.96ce6dd4ca32880ddfddd660@nifty.ne.jp> <20211106044116.698b465a5d8ed6ce2cc75c99@nifty.ne.jp> <2cfa5de7-3b95-9062-4572-f36d304bc916@cornell.edu> <20211106151047.4d8f626bd6ebe9e4d8017f3b@nifty.ne.jp> <20211110173003.88359e8482ffa8b8be326903@nifty.ne.jp> <20211110223049.b61c6cb87fb3e540b4214bcf@nifty.ne.jp> <20211111201206.72cd688ce6a0d72d3a4f6c5f@nifty.ne.jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-developers@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin core component developers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2021 08:33:49 -0000 On Thu, 11 Nov 2021 20:12:06 +0900 Takashi Yano wrote: > On Thu, 11 Nov 2021 10:52:33 +0100 > Corinna Vinschen wrote: > > What I don't like much is that we are now running a busy loop, but the > > NtQueryObject hang is... disappointing, to say the least. What about > > using another function like NtQueryInformationFile(FileNameInformation)? > > I bet this hangs, too, right? > > I have just confirmed that NtQueryInformationFile(FileNameInformation) > also hangs. I tried to utilize following APIs, however, all of them hangs. NtQueryObject(ObjectNameInformation) NtQueryInformationFile(FileNameInformation) GetFinalPathNameByHandle() GetFileInformationByHandleEx(FileNameInfo) However, NtQueryInformationFile(FileProcessIdsUsingFileInformation) does not hang. I wonder how it checks internally that one of the process handles is pointing the same pipe. -- Takashi Yano