All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v2 9/9] don't flag parent socket as RCV_SHUTDOWN if one one subflow has closed
Date: Fri, 06 Dec 2019 16:57:46 +0100	[thread overview]
Message-ID: <20191206155746.GZ795@breakpoint.cc> (raw)
In-Reply-To: a0204fbd-6678-c9ce-1273-9f6183892615@tessares.net

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

Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
> - 192c07c3fe9b: "squashed" patch 1/9 in "mptcp: Add handling of incoming
> MP_JOIN requests"
> - d6c1939a16c5..2cc726803b47: result
> - 0c24eaeadf60: "squashed" patch 2/9, part 1, in "mptcp: Add handling of
> incoming MP_JOIN requests"
> - f2a1eeb27eab: "squashed" patch 2/9, part 2, in "mptcp: Add handling of
> outgoing MP_JOIN requests"
> - 216b0b82f102: conflict in t/mptcp-introduce-MPTCP-retransmission-timer
> - e1012595cc3d: conflict in t/mptcp-add-and-use-mptcp-RTX-flag
> - 2cc726803b47..48f66afb6a81: result
> - the other patches have been added at the end. I had some conflicts with:
>  - "copy connection id from first subflow to mptcp socket"
>  - "make accept not allocate kernel socket struct"
>  - "subflow: place further subflows on new 'join_list'"
> 
> Tests on top of the commit introducing the kselftests are OK but not the one
> at the end of the series (export branch). Here is the trace (without
> CONFIG_KASAN nor PROVE_LOCKING)

I will have a look, thanks for reporting.

             reply	other threads:[~2019-12-06 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 15:57 Florian Westphal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-06 17:04 [MPTCP] Re: [PATCH v2 9/9] don't flag parent socket as RCV_SHUTDOWN if one one subflow has closed Matthieu Baerts
2019-12-06 16:37 Florian Westphal
2019-12-06 15:52 Matthieu Baerts
2019-12-03  9:13 Matthieu Baerts
2019-12-03  9:05 Paolo Abeni
2019-12-03  7:44 Matthieu Baerts
2019-12-02 21:21 Paolo Abeni

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=20191206155746.GZ795@breakpoint.cc \
    --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.