All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH 0/4] mptcp: recvmsg refactor follow-up
Date: Thu, 17 Oct 2019 11:00:35 +0200	[thread overview]
Message-ID: <cover.1571258477.git.pabeni@redhat.com> (raw)

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

This series bring in a few fixes for the recent recevmsg refactor.
The patch addressing the reported failures is 2/4, while 1/4 avoids another
issue currently observable with debug enabled (recvmsg() do busy loop on some
corner cases).
Patch 3/4 fixes another possible deadlock issue, currently not reported by
the self-tests
Finally patch 4/4 updates the MIB accounting to the new code.
patches 1-3 should be squashed into "mptcp: Implement MPTCP receive path", while
patch 4 should be quashed into "mptcp: increment MIB counters in a few places".

Notes:
- the last patch is a bit rough, at it abuses an existing MIB instead
of defining a new one, if there is no agreement about that it can be dropped.
- regardless of that, "mptcp: increment MIB counters in a few places" will
 conflict on rebase, due to the changes introduced by the previous patches.
 

Paolo Abeni (3):
  mptcp: clear data_avail flag if rtx queue is empty
  mptcp: relax map checking
  mptcp: deal better with out-of-sequence mapping
  mptcp: account unsupported DSS mapping

 net/mptcp/subflow.c | 63 +++++++++++++++++++++------------------------
 1 file changed, 30 insertions(+), 33 deletions(-)

-- 
2.21.0

                 reply	other threads:[~2019-10-17  9:00 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=cover.1571258477.git.pabeni@redhat.com \
    --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.