netdev - Re: [PATCH net 0/2] bnx2x: Fix malicious VFs indication

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] [day] [month] [year] [list]

Message-Id: <20170610.160319.846840483652390189.davem@davemloft.net>
Date:   Sat, 10 Jun 2017 16:03:19 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     Yuval.Mintz@...ium.com
Cc:     netdev@...r.kernel.org, mschmidt@...hat.com
Subject: Re: [PATCH net 0/2] bnx2x: Fix malicious VFs indication

From: Yuval Mintz <Yuval.Mintz@...ium.com>
Date: Fri, 9 Jun 2017 17:17:00 +0300

> It was discovered that for a VF there's a simple [yet uncommon] scenario
> which would cause device firmware to declare that VF as malicious -
> Add a vlan interface on top of a VF and disable txvlan offloading for
> that VF [causing VF to transmit packets where vlan is on payload].
> 
> Patch #1 corrects driver transmission to prevent this issue.
> Patch #2 is a by-product correcting PF behavior once a VF is declared
> malicious.

Series applied, thank you.