netdev - Re: [RFC PATCH v1 4/4] ixgbe: enable FDB netdevice ops

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: <4F5AE142.7050702@intel.com>
Date:	Fri, 09 Mar 2012 21:06:10 -0800
From:	John Fastabend <john.r.fastabend@...el.com>
To:	Stephen Hemminger <stephen.hemminger@...tta.com>
CC:	hadi@...erus.ca, roprabhu@...co.com, netdev@...r.kernel.org,
	mst@...hat.com, chrisw@...hat.com, davem@...emloft.net,
	gregory v rose <gregory.v.rose@...el.com>,
	kvm@...r.kernel.org, sri@...ibm.com, chealy@...co-us.com,
	jhs@...atatu.com, bhutchings@...arflare.com
Subject: Re: [RFC PATCH v1 4/4] ixgbe: enable FDB netdevice ops

On 3/9/2012 7:48 PM, Stephen Hemminger wrote:
> 
>> Enable FDB ops on ixgbe when in SR-IOV mode.
>>
>> Signed-off-by: John Fastabend <john.r.fastabend@...el.com>
> 
> Will all this break anything on the vf client? What if the vf is running
> a bridge.

No shouldn't break anything.

Actually, implementing these ops in the VF driver (ixgbevf in this
case) will allow bridging to work on the VF. Because at least on
the intel 82599 devices the VF can't be put in promiscuous mode
so bridging doesn't work as expected. With the ops implemented
we could at least get traffic forwarded correctly for addresses
that were known above the VF.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html