All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net] selftests: mptcp: fix ipv6 routing setup
Date: Fri, 14 Jan 2022 15:53:41 +0100	[thread overview]
Message-ID: <c57f38e4-d30e-ff0d-bce6-c1536ad41b6b@tessares.net> (raw)
In-Reply-To: <059912660c7f5973da40413a9384bad542047013.1642098123.git.pabeni@redhat.com>

Hi Paolo, Mat, Geliang,

On 13/01/2022 19:34, Paolo Abeni wrote:
> MPJ ipv6 selftests currently lack per link route to the server
> net. Additionally, ipv6 subflows endpoints are created without any
> interface specified. The end-result is that in ipv6 self-tests
> subflows are created all on the same link, leading to expected delays
> and sporadic self-tests failures.
> 
> Fix the issue by adding the missing setup bits.

Thank you for the patch, review and test!

Now in our tree (fixes for -net) with Mat's RvB and Geliang's R&T tags:

- 9b1eb82a3253: selftests: mptcp: fix ipv6 routing setup
- Results: 26c341404c60..a99ed2058930

Builds and tests are now in progress:

https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20220114T145330
https://github.com/multipath-tcp/mptcp_net-next/actions/workflows/build-validation.yml?query=branch:export

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

      parent reply	other threads:[~2022-01-14 14:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 18:34 [PATCH mptcp-net] selftests: mptcp: fix ipv6 routing setup Paolo Abeni
2022-01-13 23:57 ` Mat Martineau
2022-01-14  3:52   ` Geliang Tang
2022-01-14 14:53 ` Matthieu Baerts [this message]

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=c57f38e4-d30e-ff0d-bce6-c1536ad41b6b@tessares.net \
    --to=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.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.