mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ricardo B. Marlière" <rbm@suse.com>
To: "David Ahern" <dsahern@gmail.com>,
	"Fernando Fernandez Mancera" <fmancera@suse.de>,
	"Ricardo B. Marlière" <rbm@suse.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	"Shuah Khan" <shuah@kernel.org>
Cc: <netdev@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests: net: fib-onlink-tests: Set high metric for default IPv6 route
Date: Sun, 21 Dec 2025 11:59:17 -0300	[thread overview]
Message-ID: <DF3ZFGNY9DYU.HO1EOLMCRT8T@suse.com> (raw)
In-Reply-To: <9c979662-cdd9-4733-911d-b1071b7c2912@gmail.com>

On Fri Dec 19, 2025 at 12:51 PM -03, David Ahern wrote:
> On 12/19/25 7:51 AM, Fernando Fernandez Mancera wrote:
>> It would probably require some work on the test but I think it could
>> benefit from using two different network namespaces. Currently it is
>> using PEER_NS and the default. I think avoiding the default one is
>> beneficial for everyone as it ensures the state is clean and that the
>> test won't interrupt the system connectivity.
>> 
>> Other tests already do that, e.g some tests in fib_tests.sh use ns1 and
>> ns2 namespaces.
>> 
>> What do you all think?
>
> agreed.

Thanks, I'll send a new version later on this week then!

      reply	other threads:[~2025-12-21 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18 12:20 Ricardo B. Marlière
2025-12-18 16:01 ` David Ahern
2025-12-19 14:51 ` Fernando Fernandez Mancera
2025-12-19 15:51   ` David Ahern
2025-12-21 14:59     ` Ricardo B. Marlière [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=DF3ZFGNY9DYU.HO1EOLMCRT8T@suse.com \
    --to=rbm@suse.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --cc=fmancera@suse.de \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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®