mptcp: replace mptcp_disconnect with a stub

Paolo points out that mptcp_disconnect is bogus:
"lock_sock(sk);
looks suspicious (lock should be already held by the caller)
And call to: tcp_disconnect(sk, flags); too, sk is not a tcp
socket".

->disconnect() gets called from e.g. inet_stream_connect when
one tries to disassociate a connected socket again (to re-connect
without closing the socket first).
MPTCP however uses mptcp_stream_connect, not inet_stream_connect,
for the mptcp-socket connect call.

inet_stream_connect only gets called indirectly, for the tcp socket,
so any ->disconnect() calls end up calling tcp_disconnect for that
tcp subflow sk.

This also explains why syzkaller has not yet reported a problem
here.  So for now replace this with a stub that doesn't do anything.

Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/14
Acked-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
Florian Westphal 2020-04-29 20:43:20 +02:00 коммит произвёл David S. Miller
Родитель 9812307491
Коммит 42c556fef9
1 изменённых файлов: 6 добавлений и 5 удалений

Просмотреть файл

@ -1316,11 +1316,12 @@ static void mptcp_copy_inaddrs(struct sock *msk, const struct sock *ssk)
static int mptcp_disconnect(struct sock *sk, int flags) static int mptcp_disconnect(struct sock *sk, int flags)
{ {
lock_sock(sk); /* Should never be called.
__mptcp_clear_xmit(sk); * inet_stream_connect() calls ->disconnect, but that
release_sock(sk); * refers to the subflow socket, not the mptcp one.
mptcp_cancel_work(sk); */
return tcp_disconnect(sk, flags); WARN_ON_ONCE(1);
return 0;
} }
#if IS_ENABLED(CONFIG_MPTCP_IPV6) #if IS_ENABLED(CONFIG_MPTCP_IPV6)