MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH] Squash-to: "mptcp: wake-up readers only for in sequence data"
Date: Mon, 7 Jun 2021 09:45:31 -0700 (PDT)	[thread overview]
Message-ID: <46364e9-a88c-45ba-1bf1-34d4bef3faf@linux.intel.com> (raw)
In-Reply-To: <7d6fdeb1-6155-6481-70f8-ab1115317c5d@tessares.net>

On Mon, 7 Jun 2021, Matthieu Baerts wrote:

> Hi Paolo, Mat,
>
> On 07/06/2021 16:08, Paolo Abeni wrote:
>> We need to flip the DATA_READY bit under the mptcp_data_lock()
>> (or before acquiring it, as the old code did), or the BH could
>> end-up flipping the bit after that the user-space already
>> flushed the just-appended data.
>>
>> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
>
> Thank you for the patch!
>
> @Mat: I hope you don't mind if I already apply it to fix issues/201 and
> apply other patches!

No problem!

>
> - b2427404975d: "squashed" in "mptcp: wake-up readers only for in
> sequence data"
> - Results: 3c5535f65726..e5d80c7af352
>
> Builds and tests are now in progress:
>
> https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20210607T145646
> https://github.com/multipath-tcp/mptcp_net-next/actions/workflows/build-validation.yml?query=branch:export/20210607T145646

--
Mat Martineau
Intel

      reply	other threads:[~2021-06-07 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 14:08 [PATCH] Squash-to: "mptcp: wake-up readers only for in sequence data" Paolo Abeni
2021-06-07 14:57 ` Matthieu Baerts
2021-06-07 16:45   ` Mat Martineau [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=46364e9-a88c-45ba-1bf1-34d4bef3faf@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox