From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v1] Squash-to: "tcp: Prevent coalesce/collapse when skb has MPTCP extensions"
Date: Thu, 19 Dec 2019 12:43:10 +0100 [thread overview]
Message-ID: <20191219114310.GC795@breakpoint.cc> (raw)
In-Reply-To: 8d1032ab5f4006cf6554eac229596d6d4d95896f.1576752025.git.pabeni@redhat.com
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> -static inline bool mptcp_skb_ext_exist(const struct sk_buff *skb)
> +/* move the skb extension owership, with the assumption that 'to' is
> + * newly allocated and 'from' carries only MPTCP ext
> + */
> +static inline void mptcp_skb_ext_move(struct sk_buff *to,
> + struct sk_buff *from)
> +{
> + if (WARN_ON_ONCE(to->active_extensions))
> + skb_ext_put(to);
> + WARN_ON_ONCE(from->active_extensions & ~(1 << SKB_EXT_MPTCP));
This warn is triggered for skb that came in via a bridge.
I do not think you need the 2nd WARN.
> + to->active_extensions = from->active_extensions;
> + to->extensions = from->extensions;
> + from->extensions = NULL;
This NULL assignment isn't needed -- if it is, something else is broken.
Rest looks good -- I agree that sk_is_mptcp() check could
be used as you pointed out in your reply to Christoph.
Thanks for working on this.
next reply other threads:[~2019-12-19 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 11:43 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-19 11:47 [MPTCP] Re: [PATCH v1] Squash-to: "tcp: Prevent coalesce/collapse when skb has MPTCP extensions" Paolo Abeni
2019-12-19 11:12 Paolo Abeni
2019-12-19 10:54 Christoph Paasch
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=20191219114310.GC795@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.