accept: Bad address

accept: Bad address

[Ilguiz Latypov via cygwin]

Hello,

The latest Cygwin 64-bit release with the snapshot cygwin1.dll copied on top of it shows an "accept: Bad address error" in 3 reproducible cases:

(a) The sshd daemon on receiving a connection request.
(b) The XWin server on receiving a connection request from an X11 client such as xterm.
(c) The Python server receiving a TCP connection in the socket's accept().

A StackOverflow question 41018644 from December 2016 showed an example of the bug with the Python server (c).

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

Re: accept: Bad address

[Mark Geisert]

Ilguiz Latypov via cygwin wrote:
> Hello,
>
> The latest Cygwin 64-bit release with the snapshot cygwin1.dll copied on top of it shows an "accept: Bad address error" in 3 reproducible cases:
>
> (a) The sshd daemon on receiving a connection request.
> (b) The XWin server on receiving a connection request from an X11 client such as xterm.
> (c) The Python server receiving a TCP connection in the socket's accept().

That is likely a different problem with similar symptoms.

> A StackOverflow question 41018644 from December 2016 showed an example of the bug with the Python server (c).

There seems to have been a brief period of time in March where accept() was not 
working properly.  There was one report on the list (from Denis Excoffier) and 
at the same time it wasn't working for me, also using X, on a personal build of 
the Cygwin DLL from git source.  Denis later reported it working again, and I 
can confirm it is working again for me.

One option is to use the previous snapshot, dated 20180220.  The other is to 
wait until the next snapshot (after 20180309) is available.

Corinna or somebody else with the chops/access, could we get a new Cygwin DLL 
snapshot built when you have a chance?
Thanks,

..mark


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

Re: accept: Bad address

[Mark Geisert]

Mark Geisert, correcting my previous post:
Mark Geisert wrote:
> Ilguiz Latypov via cygwin wrote:
>> Hello,
>>
>> The latest Cygwin 64-bit release with the snapshot cygwin1.dll copied on top
>> of it shows an "accept: Bad address error" in 3 reproducible cases:
>>
>> (a) The sshd daemon on receiving a connection request.
>> (b) The XWin server on receiving a connection request from an X11 client such
>> as xterm.
>> (c) The Python server receiving a TCP connection in the socket's accept().
[...]
>
>> A StackOverflow question 41018644 from December 2016 showed an example of the
>> bug with the Python server (c).

That last report is likely a different problem with similar symptoms.

>
> There seems to have been a brief period of time in March where accept() was not
> working properly.
                   ^ in snapshots and Cygwin DLL built from source.  Released 
Cygwin DLLs were not affected.

 >                    There was one report on the list (from Denis Excoffier) and
> at the same time it wasn't working for me, also using X, on a personal build of
> the Cygwin DLL from git source.  Denis later reported it working again, and I
> can confirm it is working again for me.
>
> One option is to use the previous snapshot, dated 20180220.  The other is to
> wait until the next snapshot (after 20180309) is available.

Another option is to build your own Cygwin DLL from git source.

> Corinna or somebody else with the chops/access, could we get a new Cygwin DLL
> snapshot built when you have a chance?
> Thanks,

Sorry for the deficient description in my earlier post.

..mark


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

Re: accept: Bad address

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

On Apr  3 22:59, Mark Geisert wrote:
> Ilguiz Latypov via cygwin wrote:
> > Hello,
> > 
> > The latest Cygwin 64-bit release with the snapshot cygwin1.dll copied on top of it shows an "accept: Bad address error" in 3 reproducible cases:
> > 
> > (a) The sshd daemon on receiving a connection request.
> > (b) The XWin server on receiving a connection request from an X11 client such as xterm.
> > (c) The Python server receiving a TCP connection in the socket's accept().
> 
> That is likely a different problem with similar symptoms.
> 
> > A StackOverflow question 41018644 from December 2016 showed an example of the bug with the Python server (c).
> 
> There seems to have been a brief period of time in March where accept() was
> not working properly.  There was one report on the list (from Denis
> Excoffier) and at the same time it wasn't working for me, also using X, on a
> personal build of the Cygwin DLL from git source.  Denis later reported it
> working again, and I can confirm it is working again for me.

I reshuffled lots of socket code to make room for a new AF_UNIX
implementation.  While at it, I screwed up in a few places, so
socket code was broken for a bit.  The OpenSSH testsuite helped
a lot to find the bugs, btw :}

> Corinna or somebody else with the chops/access, could we get a new Cygwin
> DLL snapshot built when you have a chance?

New snapshots are up.


Corinna

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: accept: Bad address

[Ilguiz Latypov via cygwin]

On Wed, Apr 04, 2018 at 11:25:30AM +0200, Corinna Vinschen wrote:
> I reshuffled lots of socket code to make room for a new AF_UNIX
> implementation.  While at it, I screwed up in a few places, so
> socket code was broken for a bit.  The OpenSSH testsuite helped
> a lot to find the bugs, btw :}
> 
> > Corinna or somebody else with the chops/access, could we get a new Cygwin
> > DLL snapshot built when you have a chance?
> 
> New snapshots are up.

Thanks, it worked.


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