> Sure, there are some errors codes that are definitely generated by the
> current send, but there are others (EHOSTUNREACH) that may be generated
> by any packet (including the current one) and you don't know what to
> do now (resend or ignore).
He is right. It is really impossible to segregate sk->err originated
errors and fatal conditions. This flaw makes correct (f.e. free of dead loops)
send*() procedure hairy and still not 100% reliable.
I do think, that sk->err must not be reported by sendmsg()
on an unconnected socket.
BTW libresolv understands it and uses connected socket, when it is
possible. And when it uses unconnected socket, it cannot make
anything useful with error in any case.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/