From: David Ahern <dsahern@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
Peter Oskolkov <posk@google.com>,
Alexei Starovoitov <ast@kernel.org>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: Peter Oskolkov <posk@posk.io>
Subject: Re: [PATCH bpf-next] selftests: bpf: add VRF test cases to lwt_ip_encap test.
Date: Tue, 9 Apr 2019 09:57:31 -0700 [thread overview]
Message-ID: <fe4edfa2-4b0d-6c5d-6ced-c12c82cb4868@gmail.com> (raw)
In-Reply-To: <07f9be8a-7856-8b68-f085-b72c0e880a05@iogearbox.net>
On 4/9/19 2:48 AM, Daniel Borkmann wrote:
> On 04/05/2019 04:32 AM, David Ahern wrote:
>> On 4/3/19 9:43 AM, Peter Oskolkov wrote:
>>> This patch adds tests validating that VRF and BPF-LWT
>>> encap work together well, as requested by David Ahern.
>>>
>>> Signed-off-by: Peter Oskolkov <posk@google.com>
>>> ---
>>> .../selftests/bpf/test_lwt_ip_encap.sh | 134 +++++++++++-------
>>> 1 file changed, 86 insertions(+), 48 deletions(-)
>>>
>>
>> I hit a wall with running this script. One problem is the different
>> versions of nc for debian (stretch to be specific), and another problem
>> is commands failing it is hard to figure out why (e.g., connect failures
>> which seem like route lookup problems). I have been adding run_cmd and
>> PAUSE_ON_FAIL options similar to what is in fib_tests.sh and the change
>> I sent for pmtu.sh, but I have not finished.
>>
>> I am traveling tomorrow and not sure how much time I'll get this weekend
>> to come back to this. Might be early next week.
>
> Hi David, any progress on the above?
not yet.
next prev parent reply other threads:[~2019-04-09 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 15:43 [PATCH bpf-next] selftests: bpf: add VRF test cases to lwt_ip_encap test Peter Oskolkov
2019-04-04 5:09 ` Martin Lau
2019-04-04 15:04 ` David Ahern
2019-04-04 15:05 ` David Ahern
2019-04-05 2:32 ` David Ahern
2019-04-09 9:48 ` Daniel Borkmann
2019-04-09 16:57 ` David Ahern [this message]
2019-04-11 1:19 ` David Ahern
2019-04-11 1:26 ` Peter Oskolkov
2019-04-11 4:17 ` David Ahern
2019-04-11 4:38 ` Peter Oskolkov
2019-04-11 5:04 ` David Ahern
2019-04-17 2:23 ` Alexei Starovoitov
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=fe4edfa2-4b0d-6c5d-6ced-c12c82cb4868@gmail.com \
--to=dsahern@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=posk@google.com \
--cc=posk@posk.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).