Bug#645469: bind() fails for AF_UNIX sockets with EINVAL
2011/10/16 Jonathan Nieder <firstname.lastname@example.org>:
> More importantly, there is the question you raised of whether this
> should be done in userspace by libc instead. That would avoid
> upstream having to wonder, "why should we care what happens when
> someone using a BSD4.3-style bind() calls our BSD4.4-style kernel"?
> So it's tempting.
I guess upstream would appreciate if we get rid of the length limit.
It sets the maximum path length for sockets to 104 chars, is that so?