netdev - Re: [EXT] Re: [PATCH net-next] net/hanic: Add the hanic network interface for high availability links

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <CALHoRjeU_28Sm+SoYQ6NP4W0ppK+okUubWt2orwgAZ2B4RVwfw@mail.gmail.com>
Date:   Tue, 22 Nov 2022 13:01:54 -0800
From:   Steve Williams <steve.williams@...cruise.com>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Vladimir Oltean <vladimir.oltean@....com>,
        Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
        vinicius.gomes@...el.com, xiaoliang.yang_1@....com
Subject: Re: [EXT] Re: [PATCH net-next] net/hanic: Add the hanic network
 interface for high availability links

On Tue, Nov 22, 2022 at 11:55 AM Andrew Lunn <andrew@...n.ch> wrote:
>
> > ../drivers/net/hanic/hanic_sysfs.c:83:31: error: ‘struct hanic_netns’ has no member named ‘class_attr_sandlan_interfaces’; did you mean ‘class_attr_hanic_interfaces’?
> >    83 |         sysfs_attr_init(&xns->class_attr_sandlan_interfaces.attr);
>
> There was another submission over the weekend adding a network
> emulation system called sandlan. The cover latter for this patchset
> should of at minimum said there was a dependency between the two. But
> in practice, there should not be any dependency at all. It is unclear
> if sandlan will get merged.
>

Hanic does not rely on sandlan. I used sandlan as a test bed while implementing
the hanic driver, and apparently some bits leaked into this patch. I'll fix it.
-- 

Stephen Williams

Senior Software Engineer

Cruise

-- 


*Confidentiality Note:* We care about protecting our proprietary 
information, confidential material, and trade secrets. This message may 
contain some or all of those things. Cruise will suffer material harm if 
anyone other than the intended recipient disseminates or takes any action 
based on this message. If you have received this message (including any 
attachments) in error, please delete it immediately and notify the sender 
promptly.