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 Upstream <mptcp@lists.linux.dev>
Subject: Re: [Weekly meetings] MoM - 26th of August 2021
Date: Fri, 27 Aug 2021 10:37:28 -0700 (PDT)	[thread overview]
Message-ID: <1c2d3145-62e-71e7-fdb-a56e3194a125@linux.intel.com> (raw)
In-Reply-To: <4723f4cc-c9f8-26c6-9f26-35f6c2ef2975@tessares.net>

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


On Thu, 26 Aug 2021, Matthieu Baerts wrote:

> Patches to send to netdev:
>    → https://github.com/multipath-tcp/mptcp_net-next/commits/export
>    - net:
>        - mptcp: fix possible divide by zero:
>            - might be good to have feedback from syzkaller
>            - and the guy from Tencent
>            - We can send it tomorrow if we don't have negative feedback

syzkaller tests are still looking ok. Haven't heard from Jiang @ Tencent 
about test results yet. Unless I see negative tests/feedback in the next 
several hours I will send this patch and the selftest fix.

>        - selftests: mptcp: clean tmp files in simult_flows:
>            - can be sent with the other one
>        - mptcp: Only send extra TCP acks in eligible socket states:
>            - still need to wait
>
>    - net-next:
>        - MPTCP_INFO:
>            - better to send with the next version to have more time to
> fix exposed UAPI (not at the end of a release cycle)
>        - optimise incoming opt:
>            - it doesn't change any API visual aspect so it should be
> fine to send it now (or wait if we prefer)

The incoming option patches have been merged to net-next.


--
Mat Martineau
Intel

      reply	other threads:[~2021-08-27 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 18:35 [Weekly meetings] MoM - 26th of August 2021 Matthieu Baerts
2021-08-27 17:37 ` 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=1c2d3145-62e-71e7-fdb-a56e3194a125@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