mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Anders Roxell <anders.roxell@linaro.org>,
	davem@davemloft.net, shuah@kernel.org
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/net: enable fragments for fib-onlink-tests
Date: Thu, 8 Mar 2018 10:59:21 -0700	[thread overview]
Message-ID: <4ee15d22-86d6-7e9e-4820-536cb38c9027@gmail.com> (raw)
In-Reply-To: <20180308101723.19721-1-anders.roxell@linaro.org>

On 3/8/18 3:17 AM, Anders Roxell wrote:
> We miss CONFIG_* fragments so test fib-onlink-tests.sh can do:
> ip li add lisa type vrf table 1101
> ip li add veth1 type veth peer name veth2
> 
> And the follow message occurs if it isn't enabled:
> Configuring interfaces
> RTNETLINK answers: Operation not supported
> 
> This enables for NET_NRF (and friends) and VETH so we can create a vrf
> table and veth.
> 
> Fixes: 153e1b84f477 ("selftests: Add FIB onlink tests")
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
>  tools/testing/selftests/net/config | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/tools/testing/selftests/net/config b/tools/testing/selftests/net/config
> index 7177bea1fdfa..6a75a3ea44ad 100644
> --- a/tools/testing/selftests/net/config
> +++ b/tools/testing/selftests/net/config
> @@ -2,3 +2,8 @@ CONFIG_USER_NS=y
>  CONFIG_BPF_SYSCALL=y
>  CONFIG_TEST_BPF=m
>  CONFIG_NUMA=y
> +CONFIG_NET_VRF=y
> +CONFIG_NET_L3_MASTER_DEV=y
> +CONFIG_IPV6=y
> +CONFIG_IPV6_MULTIPLE_TABLES=y
> +CONFIG_VETH=y
> 

Thanks for updating the config.

The recent pmtu test needs quite a bit of additional configs as well.

      parent reply	other threads:[~2018-03-08 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 10:17 Anders Roxell
2018-03-08 16:14 ` David Miller
2018-03-08 17:59 ` David Ahern [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=4ee15d22-86d6-7e9e-4820-536cb38c9027@gmail.com \
    --to=dsahern@gmail.com \
    --cc=anders.roxell@linaro.org \
    --cc=davem@davemloft.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

all inboxes | Powered by JetHome®