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: <Y34WM8PkVvZ3Yb9y@nanopsycho>
Date:   Wed, 23 Nov 2022 13:46:43 +0100
From:   Jiri Pirko <jiri@...nulli.us>
To:     Steve Williams <steve.williams@...cruise.com>
Cc:     Vladimir Oltean <olteanv@...il.com>, netdev@...r.kernel.org
Subject: Re: [EXT] Re: [PATCH net-next] net/hanic: Add the hanic network
 interface for high availability links

Tue, Nov 22, 2022 at 09:57:46PM CET, steve.williams@...cruise.com wrote:
>On Tue, Nov 22, 2022 at 5:55 AM Vladimir Oltean <olteanv@...il.com> wrote:
>> Neither bond nor team have forwarding between ports built in, right?
>> Forwarding is pretty fundamental to 802.1CB (at least to the use cases
>> I know of).
>
>This driver also does not forward between ports. My intent wasn't to
>implement a bridge,
>but an endpoint. If forwarding between ports is desired, then perhaps
>you want a bridge?
>I think some other 802.1cb offerings on this list took that approach,
>but didn't seem to
>handle the endpoint case well.

Okay, could you then reply to my question asked earlier in this thread
why don't you implement this a part of bond/team instead of a new driver?

Thanks!


>
>-- 
>
>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.