On Thu, 2015-11-19 at 13:53 -0800, Tom Herbert wrote:
> That covers the case where the local address is removed, but the not
> the case where the network manager is informed of an error in the path
> and wants to signal the application. My understanding was that
> SIOCKILLADDR would work for the first case, but this patch was need to
> cover the second case.
>
> btw, instead of closing the TCP socket can we just report an error and
> wake up the application without affecting the connection? That is this
> just becomes an error on the socket. The response by the application
> will be the same in any case, porbablly just close the socket and try
> to reestablish the connection.
I thought this was the patch intent ?
Application gets a EPOLLIN|EPOLLOUT|POLLERR notification (if it is
willing to receive it, or blocked in a socket syscall) and closes the
socket.
sk->sk_err = ETIMEDOUT;
sk->sk_error_report(sk);
tcp_done(sk);
If this sequence is not doing the job, then we have other worries in our
stack.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
