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: RFCv2 for netdev: what's missing?
Date: Thu, 03 Oct 2019 21:21:58 +0200	[thread overview]
Message-ID: <20191003192158.GE13866@breakpoint.cc> (raw)
In-Reply-To: 01b35a0bb501816a157e9c6681d2ee59d86278af.camel@redhat.com

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

Paolo Abeni <pabeni(a)redhat.com> wrote:
> I think that:
> 
>        tcp: clean ext on tx recycle
> 
> does have some minimal mptcp dependencies that can't be removed without
> making such patch a no-op, so perhaps we should also include some very
> minimal MPTCP stub definitions:

Why?  It doesn't have any MPTCP dep.  Just zap all the extension space
and netfilter conntrack entry.

AFAICS things might already go wrong in case we get recycle skb that
has an ipsec secpath assigned, or am I missing something?

And unless there is something in place that removes skb->nfct before
the skb is placed on the socket cache, rmmod nf_conntrack can block
forever as such queued skb holds a reference on conntrack struct.

> I *think* we can also do a bolder step and send this next iteration as
> _NOT_ RFC, aiming at inclusion. My [mis]understanding is that we
> should post later chunks after the first one is merged, easily.

Hmm, we can try but I am not sure upstream would accept exposure of
some tcp core functions without a in-tree user.

             reply	other threads:[~2019-10-03 19:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 19:21 Florian Westphal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-04 11:25 [MPTCP] Re: RFCv2 for netdev: what's missing? Matthieu Baerts
2019-10-03  8:12 Paolo Abeni
2019-10-03  7:46 Florian Westphal
2019-10-03  0:39 Mat Martineau
2019-10-02 23:55 Mat Martineau
2019-10-02 23:41 Mat Martineau
2019-10-02 21:11 Matthieu Baerts
2019-10-01 23:07 Mat Martineau
2019-10-01 20:26 Paolo Abeni
2019-10-01 19:40 Matthieu Baerts
2019-10-01 19:28 Matthieu Baerts
2019-10-01 17:21 Mat Martineau
2019-10-01 16:23 Mat Martineau
2019-10-01 16:14 Peter Krystad
2019-10-01 16:07 Paolo Abeni
2019-10-01 15:34 Florian Westphal
2019-10-01 15:14 Matthieu Baerts
2019-10-01 15:07 Matthieu Baerts
2019-10-01 15:00 Florian Westphal
2019-10-01 14:58 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=20191003192158.GE13866@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.