netdev - Re: 2.6.31 ARP related problems

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: <5f2db9d90909020747k23be99d3xc27d6c668351bf60@mail.gmail.com>
Date:	Wed, 2 Sep 2009 07:47:42 -0700
From:	Alexander Duyck <alexander.duyck@...il.com>
To:	Or Gerlitz <ogerlitz@...taire.com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	netdev@...r.kernel.org, Eric Dumazet <eric.dumazet@...il.com>,
	"Duyck, Alexander H" <alexander.h.duyck@...el.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
	David Miller <davem@...emloft.net>
Subject: Re: 2.6.31 ARP related problems

I don't suspect this has much of an effect on the Virtualization use
case for SR-IOV since the VFs are meant to be direct assigned as PCI
devices to the individual VMs so they won't even show up in the
routing table.  For the most part the igbvf driver typically will be
black listed for the host kernel since it already has the PF
interface, and the driver will only be loaded on the guests.

You can probably also reproduce the issue by placing multiple physical
network interfaces on the same network segment if you saw the same
effect on SR-IOV since that is essentially the effect the VFs create
due to the switching logic built into the 82576.

Thanks,

Alex

On Wed, Sep 2, 2009 at 5:20 AM, Or Gerlitz<ogerlitz@...taire.com> wrote:
> Eric W. Biederman wrote:
>> I just tested.  If the two macvlans are in separate network namespaces all is well,
>> so definitely not macvlan. As you have observed there are no real changes to arp.c
>
> Yes, it's not macvlan to blame, I just tested it in SR-IOV scheme with igb/igbvf and
> I see the same problem, only ping that goes through / targeted to the IP address of the first
> VF device routing hit works, which means SR-IOV isn't really usable with 2.6.31 when you want
> a multiple VMs scheme, each attached to a different VF and all VMs on the same network segment.
>
>
> Or.
> --
> 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
>
--
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