X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 138DD385841F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1693060518;
	bh=LxkOyaXGUBDlC/mOHWKAIbB6ylMCMRdReHvdIQyIpZI=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=QOikxQzhD2tsBoHj7zBlURo1o2IgVfvkPcZDVMZ1O6pUnrXDBMDo13a3tb8Fh/LJJ
	 OHRyIv5VydLuEd9CQl/zpJfPPhpDrooFOXB78xrFas03DUa5KdP9LsCqITVuc6dHU9
	 X/VGQp8yb7Tx79r3meUti5ng/r+7HMqpXbcxGP1k=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 39D3F3858C33
Date: Sat, 26 Aug 2023 16:34:39 +0200
To: cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: scp stalls on uploading in cygwin 3.5 current
 master.
Message-ID: <ZOoNf5gRD5k5fjTj@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <20230824123131.390b4471915c963425c77608@nifty.ne.jp>
 <ZOcb9SKtMPTQfj/m@calimero.vinschen.de>
 <20230825174832.9ebae8112667d5d5411cb8db@nifty.ne.jp>
 <ZOiHkCWY7PK3livD@calimero.vinschen.de>
 <DM8PR09MB70957918F669340C497F48D5A5E3A@DM8PR09MB7095.namprd09.prod.outlook.com>
 <ZOidNPZSXvaecVJc@calimero.vinschen.de>
 <ZOiqR14RTnRudWP7@calimero.vinschen.de>
 <DM8PR09MB70956281C4A01D025159B72BA5E3A@DM8PR09MB7095.namprd09.prod.outlook.com>
 <ZOoDhVmqRAjWHCCa@calimero.vinschen.de>
 <DM8PR09MB7095FA791F51E71CBD906E14A5E2A@DM8PR09MB7095.namprd09.prod.outlook.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <DM8PR09MB7095FA791F51E71CBD906E14A5E2A@DM8PR09MB7095.namprd09.prod.outlook.com>
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On Aug 26 14:15, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > This thread is not about send() blocking or returning EAGAIN.  This
> > is about the behaviour of select(2) and poll(2).
> 
> I was merely commenting on your note that if select() returned a socket as
> writable, and send() writes more than internally allowed, then send() would block.
> It wouldn't!  It'd just write the allowable count, and return as a short write,
> whether the socket was blocking or not.

But that's not the situation here.  It's not helpful to get this kind of
comment without it actually referring to the context in question.  We're
coming from a select call which is implemented via Winsock-specific
network events.  Everything else is a followup and a result of this.

> select() and poll() whether I/O would block.  By the virtue of this,
> a socket, which is in error (except for EAGAIN), is writable exactly
> because write()/send() to such a socket would return -1 right away.

And that's not the case her either.


Corinna

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