>> No, as this is the current behavior. The change will be for accept
>> to return an error, on the basis that 1) most apps already do the
>> wrong thing now anyway, and 2) it brings us closer to a 'standard',
>> e.g.: what other systems are doing as well.
>
>I don't understand then.
>
>What is the problem with the current behavior? Is this just an
>optimization or a real bug fix? I'd say it's not worth changing
>if it's just an optimization, because too many things will break.
>Several apps have already been pointed out.
>
>And what do you mean by ``most apps already do the wrong thing now''?
for background (like when this happens) see previous articles
on this thread.
current behavior: return 0-length sockaddr.
many of the existing applications assumes to get valid sockaddr to
the address family of the socket (like sockaddr_in for AF_INET socket).
so if they do that, they will access uninitialized memory region,
die with assert(), whatever (BIND 9.1.0 dies with assert()).
it is rather questionable if the kernel can return 0-length sockaddr,
standard-wise, at least for connection-oriented socket.
new behavior: return ECONNABORTED.
SUSv2 suggests this behavior. it is much safer as accept(2) will fail
so almost every application will go to error case (if you don't have
error check in userland appication, that's problem in application).
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
