Pino Toscano, le Mon 11 Oct 2010 17:15:55 +0200, a écrit :
> Alle lunedì 11 ottobre 2010, Samuel Thibault ha scritto:
> > Pino Toscano, le Sun 10 Oct 2010 23:46:10 +0200, a écrit :
> > > make_sockaddr_port() calls the getname function of the sock-ops of
> > > the current sock struct, which can be o
Alle lunedì 11 ottobre 2010, Samuel Thibault ha scritto:
> Pino Toscano, le Sun 10 Oct 2010 23:46:10 +0200, a écrit :
> > make_sockaddr_port() calls the getname function of the sock-ops of
> > the current sock struct, which can be one of
> > - linux-src/net/ipv6/af_inet6.c:inet6_getname()
> > - lin
Pino Toscano, le Sun 10 Oct 2010 23:46:10 +0200, a écrit :
> make_sockaddr_port() calls the getname function of the sock-ops of the
> current sock struct, which can be one of
> - linux-src/net/ipv6/af_inet6.c:inet6_getname()
> - linux-src/net/ipv4/af_inet.c:inet_getname()
> - linux-src/net/core/so
Hi,
looking at the Python test suite output, I found an actual bug related
to getpeername(). When called on non-connected sockets, it shall return
ENOTCONN, but instead it returns -ENOTCONN. The attached testcase shows
the issue:
$ ./getpeername
, -1, -1073741881 vs 1073741881
while it shou
