netdev - Re: [net-next PATCH 1/4] fbnic: Move promisc_sync out of netdev code and into RPC path

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: <20250828102533.GV10519@horms.kernel.org>
Date: Thu, 28 Aug 2025 11:25:33 +0100
From: Simon Horman <horms@...nel.org>
To: Alexander Duyck <alexander.duyck@...il.com>
Cc: netdev@...r.kernel.org, kuba@...nel.org, kernel-team@...a.com,
	andrew+netdev@...n.ch, pabeni@...hat.com, davem@...emloft.net
Subject: Re: [net-next PATCH 1/4] fbnic: Move promisc_sync out of netdev code
 and into RPC path

On Tue, Aug 26, 2025 at 12:44:47PM -0700, Alexander Duyck wrote:
> From: Alexander Duyck <alexanderduyck@...com>
> 
> In order for us to support the BMC possibly connecting, disconnecting, and
> then reconnecting we need to be able to support entities outside of just
> the NIC setting up promiscuous mode as the BMC can use a multicast
> promiscuous setup.
> 
> To support that we should move the promisc_sync code out of the netdev and
> into the RPC section of the driver so that it is reachable from more paths.
> 
> Signed-off-by: Alexander Duyck <alexanderduyck@...com>

Reviewed-by: Simon Horman <horms@...nel.org>