lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 2 Sep 2022 11:33:31 -0700
From:   Florian Fainelli <>
To:     Vladimir Oltean <>,
        "" <>
Cc:     "" <>,
        "David S. Miller" <>,
        Eric Dumazet <>,
        Jakub Kicinski <>,
        Paolo Abeni <>,
        Vivien Didelot <>,
        Andrew Lunn <>,
        Vladimir Oltean <>,
        Claudiu Manoil <>,
        Alexandre Belloni <>,
        "" <>,
        Colin Foster <>,
        Roopa Prabhu <>,
        Nikolay Aleksandrov <>,
        Tobias Waldekranz <>,
        Marek Behún <>,
        Ansuel Smith <>,
        DENG Qingfang <>,
        Alvin Šipraga <>,
        Linus Walleij <>,
        Luiz Angelo Daros de Luca <>,
        Felix Fietkau <>, John Crispin <>,
        Sean Wang <>
Subject: Re: [PATCH net-next 0/9] DSA changes for multiple CPU ports (part 4)

On 9/2/2022 3:31 AM, Vladimir Oltean wrote:
> On Tue, Aug 30, 2022 at 10:59:23PM +0300, Vladimir Oltean wrote:
>> This series represents the final part of that effort. We have:
>> - the introduction of new UAPI in the form of IFLA_DSA_MASTER
> Call for opinions: when I resend this, should I keep rtnl_link_ops,
> or should I do what Marek attempted to do, and make the existing iflink
> between a user port and its master writable from user space?
> I'm not sure if we have that many more use cases for rtnl_link_ops..

It's a bit hard to see one right now, I agree.

> at some point I was thinking we could change the way in which dsa_loop
> probes, and allow dynamic creation of such interfaces using RTM_NEWLINK;
> but looking closer at that, it's a bit more complicated, since we'd need
> to attach dsa_loop user ports to a virtual switch, and probe all ports
> at the same time rather than one by one.

Yes, not sure the custom netlink operations would be the preferred way 
of doing that configuration, maybe module parameters and/or debugfs 
might just do?

Powered by blists - more mailing lists