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/3] mptcp: fix for ipv6-related oops
Date: Thu, 21 Nov 2019 16:41:49 +0100	[thread overview]
Message-ID: <cover.1574350681.git.pabeni@redhat.com> (raw)

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

We need to allocate a larger struct sock for mptcp v6 master sockets,
otherwise inet6_sk() will access mptcp related data instead of
struct ipv6_pinfo.

This should fix the crash reported by Matt.

The protocol.c code changes are split in 2 patches to simplify the
squashing.
(yep, I know we somewhat agreed to big giant rebase, but this specific
should be trivial).

Additionally adds some fixlet for the ipv6 tests

v1 -> v2:
 - address Matt feedback on patches 1 && 2
 - add missing mptcp_v6 proto registration (I don't know why the previous
   iteration of these patches did not explode without that!!! :(((

Paolo Abeni (3):
  selftests: fixup for IPv6 tests
  mptcp: use ipv6-specific proto struct
  mptcp/ipv6: mptcp_v6_prot needs costom destroy.

 net/mptcp/protocol.c                          | 24 +++++++++++--
 .../selftests/net/mptcp/mptcp_connect.sh      | 34 ++++++-------------
 2 files changed, 33 insertions(+), 25 deletions(-)

-- 
2.21.0

             reply	other threads:[~2019-11-21 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 15:41 Paolo Abeni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-21 12:25 [MPTCP] [PATCH 0/3] mptcp: fix for ipv6-related oops 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=cover.1574350681.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.