Re: unfilled path in getsockname() for unix sockets

[Samuel Thibault]

Pino Toscano, le Sun 04 Dec 2011 16:45:20 +0100, a écrit :
> Alle domenica 4 dicembre 2011, Samuel Thibault ha scritto:
> > Pino Toscano, le Sun 04 Dec 2011 13:14:52 +0100, a écrit :
> > > while debugging, I apparently stumbled upon a bug of getsockname()
> > > for a bound unix socket, as also the attached test program shows:
> > > sun_path is left unfilled, as also the comment of
> > > S_socket_whatis_address() in hurd/pflocal/pf.c would suggest.
> > 
> > Which is a design choice, apparently: only glibc's bind.c knows about
> > the socket path.
> 
> Hmm :-/ And there's really no way to get it later?

With the current design, I don't think it can: it's like an opened file,
you can't know where you are coming from, since it may be hardlinked in
several places for instance.

Samuel