netdev - Re: bonding: Do we need netlink events for LACP status?

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: <32499.1709620407@famine>
Date: Mon, 04 Mar 2024 22:33:27 -0800
From: Jay Vosburgh <jay.vosburgh@...onical.com>
To: Hangbin Liu <liuhangbin@...il.com>
cc: netdev@...r.kernel.org
Subject: Re: bonding: Do we need netlink events for LACP status?

Hangbin Liu <liuhangbin@...il.com> wrote:

>A customer asked to add netlink event notifications for LACP bond state
>changes. With this, the network monitor could get the LACP state of bonding
>and port interfaces, and end user may change the down link port based
>on the current LACP state. Do you think if this is a reasonable case
>and do able? If yes, I will add it to my to do list.

	I think I'm going to need some more detail here.

	To make sure I understand, the suggestion here is to add netlink
notifications for transitions in the LACP mux state machine (ATTACHED,
COLLECTING, DISTRIBUTING, et al), correct?  If not, then what
specifically do you mean?

	Also, what does "change the down link port" mean?

	-J

---
	-Jay Vosburgh, jay.vosburgh@...onical.com