delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2020/11/30/12:20:06

X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 61EC03857820
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
header.from=huarp.harvard.edu
Authentication-Results: sourceware.org;
spf=pass smtp.mailfrom=allen AT huarp DOT harvard DOT edu
Subject: Re: Unix Domain Socket Limitation?
To: Ken Brown <kbrown AT cornell DOT edu>
References: <71490665-31b0-f63c-74da-461a053fac21 AT huarp DOT harvard DOT edu>
<55ea1649-1979-6238-75ab-69100c22e069 AT cornell DOT edu>
<4260ad1b-4ab2-fa36-fd0e-7c9644560114 AT huarp DOT harvard DOT edu>
<38a82f82-1ef9-768e-7d3e-15f63147e188 AT cornell DOT edu>
From: Norton Allen <allen AT huarp DOT harvard DOT edu>
Message-ID: <a1f6e9af-7c0b-4d3f-4198-1c7bff4869dc@huarp.harvard.edu>
Date: Mon, 30 Nov 2020 12:19:16 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <38a82f82-1ef9-768e-7d3e-15f63147e188@cornell.edu>
X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS,
TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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>
Cc: cygwin <cygwin AT cygwin DOT com>
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 0AUHJdin004820

On 11/26/2020 12:13 PM, Ken Brown wrote:
> [Adding the Cygwin list back to the Cc.]
>
> On 11/26/2020 11:27 AM, Norton Allen wrote:
>> On 11/25/2020 5:27 PM, Ken Brown via Cygwin wrote:
>>> On 11/25/2020 4:47 PM, Norton Allen wrote:
>>>> In my recent tests, it appears as though it is not possible to 
>>>> successfully connect via two Unix Domain sockets from one client 
>>>> application to one server application.
>>>>
>>>> Specifically, if I create a server which listens on a Unix Domain 
>>>> socket and a client, which attempts to connect() twice, both seem 
>>>> to lock up. This is not the behavior under Linux.
>>>>
>>>> I will be happy to work up a minimal example if it is helpful in 
>>>> tracking this down. I wanted to start by asking whether this is a 
>>>> known limitation and/or if there is something about the Cygwin 
>>>> implementation that makes this sort of thing very difficult.
>>>
>>> A minimal example would be extremely helpful.
>>>
>>> Corinna can answer questions about limitations in the current 
>>> implementation. But there is a new implementation under development. 
>>> It's in the topic/af_unix branch of the Cygwin git repository if 
>>> you're interested in looking at it.
>>>
>>> Corinna began working on this a couple years ago, and I've recently 
>>> been trying to finish it.  I've made quite a bit of progress, but 
>>> there's still more to do and undoubtedly many bugs. So any test 
>>> cases you have would be very useful. 
>>
>> Thanks Ken,
>>
>> As it happens, attempting to produce a minimal example suggests my 
>> problem may be somewhere else. I think I've worked in most of the 
>> features of my application one by one but have not yet revealed a 
>> failure.
>
> OK.  But if you ever do have occasion to write small test programs 
> involving AF_UNIX sockets, please send them on.  The new AF_UNIX code 
> needs as much testing as it can get.
>
I have finally put together a start of a minimal example, although it 
seems to require a certain level of complexity before tripping on the 
bug. At the moment, I do not believe the issue is related to having 
multiple sockets between the client and server. I am thinking it is some 
sort of race condition related to non-blocking sockets, since I have 
only observed it when both the client and server are using non-blocking 
sockets.

I have yet to plunge into cygwin.dll, but I think I have reached that point.

Here is the code: https://github.com/nthallen/cygwin_unix

Since I have only exercised this on my machine, I would be very 
interested to know if it is reproducible on anyone else's.


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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019