From: Paolo Abeni <pabeni@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, mathew.j.martineau@linux.intel.com,
matthieu.baerts@tessares.net, kuba@kernel.org, cpaasch@apple.com,
fw@strlen.de
Subject: Re: [PATCH net 0/3] mptcp: fix races on accept()
Date: Tue, 21 Apr 2020 10:38:28 +0200 [thread overview]
Message-ID: <a708ac7ff0119d07c2a0873d05f840982179441b.camel@redhat.com> (raw)
In-Reply-To: <20200420.130215.721617466987117194.davem@davemloft.net>
On Mon, 2020-04-20 at 13:02 -0700, David Miller wrote:
> From: Paolo Abeni <pabeni@redhat.com>
> Date: Mon, 20 Apr 2020 16:25:03 +0200
>
> > This series includes some fixes for accept() races which may cause inconsistent
> > MPTCP socket status and oops. Please see the individual patches for the
> > technical details.
>
> Series applied, thanks.
>
> It seems like patch #3 might be relevant for v5.6 -stable, what's the
> story here?
Yes, it addresses a race condition present since cc7972ea1932 ("mptcp:
parse and emit MP_CAPABLE option according to v1 spec"). I see now that
the changelog is probably a bit too vague, I'm sorry.
Cheers,
Paolo
prev parent reply other threads:[~2020-04-21 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 14:25 [PATCH net 0/3] mptcp: fix races on accept() Paolo Abeni
2020-04-20 14:25 ` [PATCH net 1/3] mptcp: handle mptcp listener destruction via rcu Paolo Abeni
2020-04-20 14:25 ` [PATCH net 2/3] mptcp: avoid flipping mp_capable field in syn_recv_sock() Paolo Abeni
2020-04-20 14:25 ` [PATCH net 3/3] mptcp: drop req socket remote_key* fields Paolo Abeni
2020-04-20 20:05 ` Mat Martineau
2020-04-21 8:24 ` Paolo Abeni
2020-04-20 20:02 ` [PATCH net 0/3] mptcp: fix races on accept() David Miller
2020-04-21 8:38 ` Paolo Abeni [this message]
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=a708ac7ff0119d07c2a0873d05f840982179441b.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=cpaasch@apple.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).