From: Song Liu <liu.song.a23@gmail.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
shuah@kernel.org, Networking <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests: bpf: enable NET_SCHED
Date: Mon, 25 Jun 2018 09:49:55 -0700 [thread overview]
Message-ID: <CAPhsuW5fMyJeuU4EMdJ_zgkZgEz2emEU42qxx_etLigRSFzXPQ@mail.gmail.com> (raw)
In-Reply-To: <20180625145605.13726-1-anders.roxell@linaro.org>
On Mon, Jun 25, 2018 at 7:56 AM, Anders Roxell <anders.roxell@linaro.org> wrote:
> CONFIG_NET_SCHED wasn't enabled in arm64's defconfig only for x86.
> So bpf/test_tunnel.sh tests fails with:
> RTNETLINK answers: Operation not supported
> RTNETLINK answers: Operation not supported
> We have an error talking to the kernel, -1
> Enable NET_SCHED and more tests passes.
>
> Fixes: 3bce593ac06b ("selftests: bpf: config: add config fragments")
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
Acked-by: Song Liu <songliubraving@fb.com>
> ---
> tools/testing/selftests/bpf/config | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/bpf/config b/tools/testing/selftests/bpf/config
> index 1e0c547caf3c..7a6d92562dc6 100644
> --- a/tools/testing/selftests/bpf/config
> +++ b/tools/testing/selftests/bpf/config
> @@ -6,6 +6,7 @@ CONFIG_TEST_BPF=m
> CONFIG_CGROUP_BPF=y
> CONFIG_NETDEVSIM=m
> CONFIG_NET_CLS_ACT=y
> +CONFIG_NET_SCHED=y
> CONFIG_NET_SCH_INGRESS=y
> CONFIG_NET_IPIP=y
> CONFIG_IPV6=y
> --
> 2.18.0
>
next prev parent reply other threads:[~2018-06-25 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 14:56 [PATCH] selftests: bpf: enable NET_SCHED Anders Roxell
2018-06-25 16:49 ` Song Liu [this message]
2018-06-26 10:07 ` Daniel Borkmann
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=CAPhsuW5fMyJeuU4EMdJ_zgkZgEz2emEU42qxx_etLigRSFzXPQ@mail.gmail.com \
--to=liu.song.a23@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
/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).