netdev - Re: [iwl-next v1] ice: only allow Tx promiscuous for multicast

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: <20241019081152.GH1697@kernel.org>
Date: Sat, 19 Oct 2024 09:11:52 +0100
From: Simon Horman <horms@...nel.org>
To: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>
Cc: intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
	brett.creeley@....com, mateusz.polchlopek@...el.com
Subject: Re: [iwl-next v1] ice: only allow Tx promiscuous for multicast

On Thu, Oct 17, 2024 at 09:08:16AM +0200, Michal Swiatkowski wrote:
> From: Brett Creeley <brett.creeley@...el.com>
> 
> Currently when any VF is trusted and true promiscuous mode is enabled on
> the PF, the VF will receive all unicast traffic directed to the device's
> internal switch. This includes traffic external to the NIC and also from
> other VSI (i.e. VFs). This does not match the expected behavior as
> unicast traffic should only be visible from external sources in this
> case. Disable the Tx promiscuous mode bits for unicast promiscuous mode.
> 
> Reviewed-by: Mateusz Polchlopek <mateusz.polchlopek@...el.com>
> Signed-off-by: Brett Creeley <brett.creeley@...el.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>

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