From: John Fastabend <john.fastabend@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
John Fastabend <john.fastabend@gmail.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>, bpf <bpf@vger.kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Jussi Maki <joamaki@gmail.com>
Subject: Re: sockmap test is broken
Date: Wed, 17 Nov 2021 10:00:11 -0800 [thread overview]
Message-ID: <6195432baf114_1f40a208aa@john.notmuch> (raw)
In-Reply-To: <CAEf4Bza3OC1pAvVvwoPhyuixf8_VpA1w0F7HAsX09x2DSYbYbA@mail.gmail.com>
Andrii Nakryiko wrote:
> On Sun, Nov 14, 2021 at 9:21 PM John Fastabend <john.fastabend@gmail.com> wrote:
> >
> > Alexei Starovoitov wrote:
> > > test_maps is failing in bpf tree:
> > >
> > > $ ./test_maps
> > > Failed sockmap recv
> > >
> > > and causing BPF CI to stay red.
> > >
> > > Since bpf-next is fine, I suspect it is one of John's or Jussi's patches.
> > >
> > > Please take a look.
> >
> > I'll look into it thanks.
>
> Any updates, John? Should we just disable test_maps in CI to make it
> useful again?
I'm debugging this now. Hopefully I'll have a fix shortly (today I hope).
Maybe, it makes sense to wait for EOD and if I still don't have the fix
disable it then. Anyways fixing it is top of list now.
>
> >
> > .John
next prev parent reply other threads:[~2021-11-17 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 18:43 sockmap test is broken Alexei Starovoitov
2021-11-15 5:21 ` John Fastabend
2021-11-15 19:54 ` sunyucong
2021-11-17 17:48 ` Andrii Nakryiko
2021-11-17 18:00 ` John Fastabend [this message]
2021-11-17 18:08 ` Andrii Nakryiko
2021-11-18 5:20 ` John Fastabend
2021-11-19 18:18 ` John Fastabend
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=6195432baf114_1f40a208aa@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=joamaki@gmail.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.