From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH] mptcp: dispose initial struct socket when its subflow is closed
Date: Thu, 11 Feb 2021 19:20:04 +0100 [thread overview]
Message-ID: <20210211182004.GB2766@breakpoint.cc> (raw)
In-Reply-To: 20210211162607.10780-1-fw@strlen.de
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
Florian Westphal <fw(a)strlen.de> wrote:
> Christoph Paasch reported following crash:
> dst_release underflow
> WARNING: CPU: 0 PID: 1319 at net/core/dst.c:175 dst_release+0xc1/0xd0 net/core/dst.c:175
> CPU: 0 PID: 1319 Comm: syz-executor217 Not tainted 5.11.0-rc6af8e85128b4d0d24083c5cac646e891227052e0c #70
> Call Trace:
> rt_cache_route+0x12e/0x140 net/ipv4/route.c:1503
> rt_set_nexthop.constprop.0+0x1fc/0x590 net/ipv4/route.c:1612
> __mkroute_output net/ipv4/route.c:2484 [inline]
> ...
>
> Problem is that worker leaves msk->subflow alone even when it
> happened to close the subflow ssk associated with it.
>
> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/157
> Reported-by: Christoph Paasch <cpaasch(a)apple.com>
> Suggested-by: Paolo Abeni <pabeni(a)redhat.com>
> Signed-off-by: Florian Westphal <fw(a)strlen.de>
> ---
> net/mptcp/protocol.c | 20 ++++++++++++++------
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
> index d49e0efbdd50..c30dff10ed9a 100644
> --- a/net/mptcp/protocol.c
> +++ b/net/mptcp/protocol.c
> @@ -2106,6 +2106,14 @@ static struct sock *mptcp_subflow_get_retrans(const struct mptcp_sock *msk)
> return backup;
> }
>
> +static void mptcp_dispose_initial_subflowg(struct mptcp_sock *msk)
> +{
Grrr. This should be 'mptcp_dispose_initial_subflow'.
Also note that msk->first also needs treatment, but I'd do that
in another patch.
reply other threads:[~2021-02-11 18:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210211182004.GB2766@breakpoint.cc \
--to=mptcp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox