X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 30 Apr 2008 20:57:48 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem with cygserver and sysv message queues: msgsnd() 	blocks  forever.
Message-ID: <20080430185747.GX23852@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <FE57175CCE23E5419899C1B0CFA26FAD0C4160959C AT EXMBXSD DOT dm DOT solekai DOT com> <20080430105846 DOT GO23852 AT calimero DOT vinschen DOT de> <FE57175CCE23E5419899C1B0CFA26FAD0C41609623 AT EXMBXSD DOT dm DOT solekai DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FE57175CCE23E5419899C1B0CFA26FAD0C41609623@EXMBXSD.dm.solekai.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Apr 30 10:16, Williams, David wrote:
> Yes, I can patch and build the sources, and will test the patch. I
> can see that this will work, and is probably the least disruptive
> way to fix it. I'm bothered a little bit by the fixed timeout value,
> although this is an exceptional case, which shouldn't occur in a
> properly tuned and managed system.

I'm not that concerned.  A fixed value of 50 will interrupt a maximum of
20 times per second.  The hz value in BSD is usually higher.  I think 50
is a good compromise.

> My thoughts for a fix were centered around replacing the msqptr
> ident parameter with a resource specific identifier that would
> allow freeing a resource by one queue to wake another. However,
> such a fix would require much regression testing, and STILL might
> need a timeout like this as an ultimate safety net. Besides, we
> likely want to continue tracking the BSD source.

There's surely some better way to solve this problem but if there's
an upstream fix, I'd like to use it.  My goal is to keep the code as
much upstream centered as possible.

> I'm currently building and testing using the cygwin-1.5.25-12 release
> tarball. Would it be more helpful for me to pull the CVS head down
> to test this?

Shouldn't matter, actually.  There's no difference in the message queue
code between 1.5.25 and CVS HEAD.  However, the bugfix will only go into
CVS HEAD.  If you need this bugfix desperately, please maintain your
local version for now.

> Thanks for the quick reply. I'm glad to be of some help.

You're welcome.  Thanks for the debugging effort and the testcase.
You almost did all the work yourself already, I just had to look
what upstream is doing about it :)

I'll check this in in a couple of minutes.


Thanks again,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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