X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 423943853809
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1648179825;
	bh=XV502IlVx2HlezNGT33nP13U/MLW78qpLEOU+O2+CGw=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=AuFh9Zq98Grxta8+SAnUG2QiFhz5S0p0Vu94xasPixE1Oq0Cal1kOre61kNt0FL67
	j3NcNnRBhgHiEvtIMX/A+VO7JnfsTqEFNudPydcf6YPrbleX+HlEJAZsApKchFZfoE
	+92aPwyt0jGySn9/3D+CKMymZQrChN8JxwS8w7/0=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org BE2783865C28
Date:	Thu, 24 Mar 2022 20:42:50 -0700 (PDT)
X-X-Sender:	jeremyd AT resin DOT csoft DOT net
To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Subject:	Re: pipe hang issue when running as SYSTEM
In-Reply-To:	<20220322221756.2b7e80ec0a51e7ebd9df5a53@nifty.ne.jp>
Message-ID:	<alpine.BSO.2.21.2203242039010.56460@resin.csoft.net>
References:	<alpine DOT BSO DOT 2 DOT 21 DOT 2203211141320 DOT 56460 AT resin DOT csoft DOT net>
	<20220322191807 DOT 8348f074683c127b1723c5c2 AT nifty DOT ne DOT jp>
	<20220322221756 DOT 2b7e80ec0a51e7ebd9df5a53 AT nifty DOT ne DOT jp>
User-Agent:	Alpine 2.21 (BSO 202 2017-01-01)
MIME-Version:	1.0
X-Spam-Status:	No, score=-4.4 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP,
	T_SCC_BODY_TEXT_LINE 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 AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Jeremy Drake via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Jeremy Drake <cygwin AT jdrake DOT com>
Cc:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Tue, 22 Mar 2022, Takashi Yano wrote:

> > Thanks for the report. This is expected problem as mentioned
> > in b531d6b commit message. However, I could not imagin the
> > situation that the service has multiple writer for the pipe
> > and one of them is a non-cygwin app.
> >
> > Question is: Does the docker invoke the command using SYSTEM
> > account? Or is the processes in docker determined as running
> > as a service?
>
> I confirmed the processes in Windows docker are running as
> well_known_service_sid. Let me consider a while.
>

Just got another report to MSYS2 of this behavior, this time from a Gitlab
CI runner that is running as a service and trying to pipe output from
Microsoft cl.exe while running configure.  This user reports that 3.3.4
with your "[PATCH v2] Cygwin: pipe: Avoid deadlock for non-cygwin writer."
applied to it does not solve the problem.

https://github.com/msys2/MSYS2-packages/issues/2893

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -