netdev - Re: [PATCH net-next 2/4] net/mlx4: Preparation for VST QinQ

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]

Date:	Thu, 7 Jul 2016 23:02:47 +0300
From:	Or Gerlitz <gerlitz.or@...il.com>
To:	Tariq Toukan <tariqt@...lanox.com>
Cc:	"David S. Miller" <davem@...emloft.net>,
	Linux Netdev List <netdev@...r.kernel.org>,
	Eran Ben Elisha <eranbe@...lanox.com>,
	Moshe Shemesh <moshe@...lanox.com>
Subject: Re: [PATCH net-next 2/4] net/mlx4: Preparation for VST QinQ

On Wed, Jul 6, 2016 at 3:29 PM, Tariq Toukan <tariqt@...lanox.com> wrote:
> From: Moshe Shemesh <moshe@...lanox.com>
>
> Check device capability to support VST QinQ mode.
> Add vport attribute vlan protocol.
> Init vport vlan protocol by default to 802.1Q.
> Add update QP support for VST QinQ.


> Add func capability vlan_offload_disable to disable all
> vlan HW acceleration on VF while the VF is set to VST QinQ mode.

this part (above two lines) is code running in the VF Eth driver,
correct? if this is indeed the case, break the patch to two (1) PF
core driver  (2) VF core/EN driver

What happens if the VF doesn't work as you expect? e.g the PF runs
your code and the VF driver is unpatched?