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 net 0/4] mptcp: a bunch of assorted fixes
Date: Wed, 16 Dec 2020 12:48:31 +0100	[thread overview]
Message-ID: <cover.1608114076.git.pabeni@redhat.com> (raw)

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

This series pulls a few fixes for the MPTCP datapath.
Most issues addressed here has been recently introduced
with the recent reworks, with the notable exception of
the first patch, which addresses an issue present since
the early days

Paolo Abeni (4):
  mptcp: fix security context on server socket
  mptcp: properly annotate nested lock
  mptcp: push pending frames when subflow has free space
  mptcp: fix pending data accounting

 net/mptcp/options.c                               | 13 ++++++++-----
 net/mptcp/protocol.c                              | 11 ++++++-----
 net/mptcp/protocol.h                              |  2 +-
 tools/testing/selftests/net/mptcp/simult_flows.sh |  6 +++---
 4 files changed, 18 insertions(+), 14 deletions(-)

-- 
2.26.2

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	mptcp@lists.01.org
Subject: [PATCH net 0/4] mptcp: a bunch of assorted fixes
Date: Wed, 16 Dec 2020 12:48:31 +0100	[thread overview]
Message-ID: <cover.1608114076.git.pabeni@redhat.com> (raw)

This series pulls a few fixes for the MPTCP datapath.
Most issues addressed here has been recently introduced
with the recent reworks, with the notable exception of
the first patch, which addresses an issue present since
the early days

Paolo Abeni (4):
  mptcp: fix security context on server socket
  mptcp: properly annotate nested lock
  mptcp: push pending frames when subflow has free space
  mptcp: fix pending data accounting

 net/mptcp/options.c                               | 13 ++++++++-----
 net/mptcp/protocol.c                              | 11 ++++++-----
 net/mptcp/protocol.h                              |  2 +-
 tools/testing/selftests/net/mptcp/simult_flows.sh |  6 +++---
 4 files changed, 18 insertions(+), 14 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-12-16 11:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 11:48 Paolo Abeni [this message]
2020-12-16 11:48 ` [PATCH net 0/4] mptcp: a bunch of assorted fixes Paolo Abeni
2020-12-17 18:30 ` patchwork-bot+netdevbpf
2020-12-16 11:48 [MPTCP] [PATCH net 1/4] mptcp: fix security context on server socket Paolo Abeni
2020-12-16 11:48 ` Paolo Abeni
2020-12-16 11:48 [MPTCP] [PATCH net 2/4] mptcp: properly annotate nested lock Paolo Abeni
2020-12-16 11:48 ` Paolo Abeni
2020-12-16 11:48 [MPTCP] [PATCH net 3/4] mptcp: push pending frames when subflow has free space Paolo Abeni
2020-12-16 11:48 ` Paolo Abeni
2020-12-16 11:48 [MPTCP] [PATCH net 4/4] mptcp: fix pending data accounting Paolo Abeni
2020-12-16 11:48 ` Paolo Abeni
2020-12-16 23:36 [MPTCP] Re: [PATCH net 1/4] mptcp: fix security context on server socket Mat Martineau
2020-12-16 23:36 ` Mat Martineau
2020-12-16 23:37 [MPTCP] Re: [PATCH net 2/4] mptcp: properly annotate nested lock Mat Martineau
2020-12-16 23:37 ` Mat Martineau

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.1608114076.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.