All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH mptcp] squashto: mptcp: protect the rx path with the msk socket spinlock
Date: Fri, 20 Nov 2020 14:18:31 +0100	[thread overview]
Message-ID: <20201120131831.GA1831@breakpoint.cc> (raw)
In-Reply-To: 5f06de0671cc23d9be8723cd9ed7f8a15d21ddeb.camel@redhat.com

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

Paolo Abeni <pabeni(a)redhat.com> wrote:
> > diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
> > index 92236a2ccbea..e62d34034d9e 100644
> > --- a/net/mptcp/protocol.c
> > +++ b/net/mptcp/protocol.c
> > @@ -2707,7 +2707,9 @@ void mptcp_destroy_common(struct mptcp_sock *msk)
> >  
> >  	__mptcp_clear_xmit(sk);
> >  
> > -	skb_queue_splice_tail_init(&sk->sk_receive_queue, &msk->receive_queue);
> > +	/* move to sk_receive_queue, sk_stream_kill_queues will purge it */
> > +	skb_queue_splice_tail_init(&msk->receive_queue, &sk->sk_receive_queue);
> > +
> >  	skb_rbtree_purge(&msk->out_of_order_queue);
> >  	mptcp_token_destroy(msk);
> >  	mptcp_pm_free_anno_list(msk);
> 
> 
> LGTM, thanks for catching this!
> 
> Not sure why self-tests did non complain loudly here ?!?

Probably all test cases drain the rx queue completely before exiting,
we might need something new to cover this.

That being said, packetdrill tests catch it but I suppose those do not
run as frequently as the kselftest infra.

             reply	other threads:[~2020-11-20 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 13:18 Florian Westphal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-20 17:14 [MPTCP] Re: [PATCH mptcp] squashto: mptcp: protect the rx path with the msk socket spinlock Matthieu Baerts
2020-11-20  8:57 Paolo Abeni

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=20201120131831.GA1831@breakpoint.cc \
    --to=unknown@example.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.