netdev - Re: [PATCH net-next v4 2/2] ipoib: show VF broadcast address

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: <20190618.104037.359105025150148890.davem@davemloft.net>
Date:   Tue, 18 Jun 2019 10:40:37 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     dledford@...hat.com
Cc:     kda@...ux-powerpc.org, netdev@...r.kernel.org,
        linux-rdma@...r.kernel.org, mkubecek@...e.cz
Subject: Re: [PATCH net-next v4 2/2] ipoib: show VF broadcast address

From: Doug Ledford <dledford@...hat.com>
Date: Tue, 18 Jun 2019 13:29:59 -0400

> On Tue, 2019-06-18 at 10:08 -0700, David Miller wrote:
>> From: Denis Kirjanov <kda@...ux-powerpc.org>
>> Date: Mon, 17 Jun 2019 10:53:41 +0200
>> 
>> > in IPoIB case we can't see a VF broadcast address for but
>> > can see for PF
>> 
>> I just want to understand why this need to see the VF broadcast
>> address is IPoIB specific?
> 
> A VF might or might not have the same security domain (P_Key) as the
> parent, and the P_Key is encoded in the broadcast address.  In the
> event that two vfs or a vf and a pf can't see each other over the IPoIB
> network, it is necessary to be able to see the broadcast address in use
> by each to make sure they are the same and not that they shouldn't be
> able to see each other because they are on different P_Keys and
> therefore different broadcast multicast groups.

Thanks for explaining.

I'll apply these to net-next right now then.

Thanks again.