DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=Auav
	acAIEugu7l2m3SxnxfM9z8axKdYAGSZvMXa0Rdq3n+mt7+3NMCQr1ik5fv63N2Ix
	ZJFSIQTBiUDvX8Dc3ejWAtBE1QvMj8iAmeZe/lF8dofA2OFdvbq3R8LM8BTvsbXi
	W9uIJA9nHC0phjvxZihO290t3b2imc9zq5IzScE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sat, 6 May 2017 20:27:47 -0700
From: Noah Misch <noah@leadboat.com>
To: cygwin@cygwin.com
Subject: Re: cygserver - Postgres Multiple connection Load Testing - Inifinte Loop
Message-ID: <20170507032747.GA876495@rfd.leadboat.com>
References: <200408030333.i733XEXn023894@mx3.redhat.com> <20040803100612.GP31522@cygbert.vinschen.de> <20170321025614.GA2100214@tornado.leadboat.com> <20170324171101.GI29995@calimero.vinschen.de> <20170328052652.GA2351961@tornado.leadboat.com> <20170402023624.GA2561924@tornado.leadboat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170402023624.GA2561924@tornado.leadboat.com>
User-Agent: Mutt/1.5.24 (2015-08-30)

On Sat, Apr 01, 2017 at 10:36:24PM -0400, Noah Misch wrote:
> On Tue, Mar 28, 2017 at 01:26:52AM -0400, Noah Misch wrote:
> > On Fri, Mar 24, 2017 at 06:11:01PM +0100, Corinna Vinschen wrote:
> > > I pushed a patchset now, and uploaded new developer snapshots for
> > > testing to https://cygwin.com/snapshots/
> > 
> > > Please give it a try
> 
> > I call the cygwin-20170324 freezes "limited" because the symptoms differ from
> > the classic freeze I described upthread.  "strace /bin/true" and "cat
> > /proc/sysvipc/sem" do not hang, but every PostgreSQL backend process is stuck
> > waiting on a synchronization primitive.
> > 
> > I can distill another self-contained test case for the limited freeze seen in
> > cygwin-20170324, but that make take awhile.  I'm sending this early report so
> > you're aware of the possible regression in cygwin-20170324.
> 
> I'm attaching a new test program that demonstrates the regression.  My previous
> test program created sixteen processes that each picked a random semaphore to
> lock.  Now, each process picks two semaphores and locks them in order.  This
> proceeds smoothly on GNU/Linux and on cygwin-20170321.tar.xz "cygserver -r 40".
> It freezes within one second on cygwin-20170324.tar.xz "cygserver -r 40".

I suggest reverting the cygwin-20170324 cygserver changes for now.  Older
versions can be configured to have reliable sysv semaphores, but I think no
settings render sysv semaphores reliable in Cygwin 2.8.0.  What do you think?

--
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