netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Andrew Lunn <andrew@lunn.ch>, Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: netdevsim: Support setting dev->perm_addr
Date: Tue, 04 Feb 2025 11:30:45 +0100	[thread overview]
Message-ID: <877c66ypbe.fsf@toke.dk> (raw)
In-Reply-To: <4b9a6e08-df15-44c1-accd-8f157c62849f@lunn.ch>

Andrew Lunn <andrew@lunn.ch> writes:

> On Mon, Feb 03, 2025 at 02:39:58PM -0800, Jakub Kicinski wrote:
>> On Mon, 03 Feb 2025 18:21:24 +0100 Toke Høiland-Jørgensen wrote:
>> > Network management daemons that match on the device permanent address
>> > currently have no virtual interface types to test against.
>> > NetworkManager, in particular, has carried an out of tree patch to set
>> > the permanent address on netdevsim devices to use in its CI for this
>> > purpose.
>> > 
>> > To support this use case, add a debugfs file for netdevsim to set the
>> > permanent address to an arbitrary value.
>> 
>> netdevsim is not for user space testing. We have gone down the path
>> of supporting random features in it already, and then wasted time trying
>> to maintain them thru various devlink related perturbations, just to
>> find out that the features weren't actually used any more.
>> 
>> NetworkManager can do the HW testing using virtme-ng.
>> 
>> If you want to go down the netdevsim path you must provide a meaningful 
>> in-tree test, but let's be clear that we will 100% delete both the test
>> and the netdevsim functionality if it causes any issues.
>
> Hi Toke
>
> What are your actual requirements? A permanent address is not expected
> to change, it is by definition, permanent. Could it be hard coded in
> netdevsim that the first instance created gets the MAC address
> 24:42:42:42:42:42? And maybe to make testing a bit more evil, keep the
> current behaviour that the actually used MAC is random, since that MAC
> address is not permanent.

I believe that would work, yeah. AFAIU, we just need some virtual device
that has the permanent address field set at all. I'll check with the NM
folks and respin with a static value, assuming this works for them.
Thanks for the suggestion!

-Toke


  reply	other threads:[~2025-02-04 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 17:21 [PATCH net-next] net: netdevsim: Support setting dev->perm_addr Toke Høiland-Jørgensen
2025-02-03 22:39 ` Jakub Kicinski
2025-02-03 23:04   ` Andrew Lunn
2025-02-04 10:30     ` Toke Høiland-Jørgensen [this message]
2025-02-04 11:20   ` Toke Høiland-Jørgensen
2025-02-04 16:56     ` Jakub Kicinski
2025-02-05  9:05       ` Toke Høiland-Jørgensen
2025-02-05 17:00         ` Jakub Kicinski
2025-02-05 17:08           ` Eric Dumazet
2025-02-05 19:13             ` Jakub Kicinski
2025-02-17 13:11 ` Jiri Pirko

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=877c66ypbe.fsf@toke.dk \
    --to=toke@redhat.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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).