netdev - Re: [PATCH v4 for-next 00/12] Add network namespace support in the RDMA-CM

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Jun 2015 17:48:11 -0600
From:	Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To:	Or Gerlitz <gerlitz.or@...il.com>
Cc:	Doug Ledford <dledford@...hat.com>,
	Haggai Eran <haggaie@...lanox.com>,
	Or Gerlitz <ogerlitz@...lanox.com>,
	"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
	Linux Netdev List <netdev@...r.kernel.org>,
	Liran Liss <liranl@...lanox.com>,
	Guy Shapiro <guysh@...lanox.com>,
	Shachar Raindel <raindel@...lanox.com>,
	Yotam Kenneth <yotamke@...lanox.com>
Subject: Re: [PATCH v4 for-next 00/12] Add network namespace support in the
 RDMA-CM

On Wed, Jun 03, 2015 at 11:07:37PM +0300, Or Gerlitz wrote:

> > I'm mostly fine with it as an optional capability, similar to macvlan,
> > I just don't see how to cleanly integrate it with RDMA CM and
> > namespaces. And I don't see what RDMA CM is supposed to do when
> > it hits this case.
> >
> > So, any ideas that don't involve the searching for IP hack??
> >
> > [And yes, as discussed with Haggie, it is not the worst hack in the
> >  world, and maybe we can live with it, but lets understand the trade
> >  offs carefully]
> 
> As Haggai wrote, if we let the using IP address thing to fly up, we have
> support for RDMA in containers using the RDMA-CM at IPoIB environments.
> This will let people test, use, experiment, fix, interact (and even
> production-it when static IP address assignment scheme is used).

I just noticed ipvlan got merged a few months ago.. That certainly
changed my view on this topic. It is basically a software
version of the same-guid ipoib children scheme. Similar issues: Same MAC
address as the parent, IPv6 SLAAC is disabled (?),  DHCP has similar
issue (solved with RFC4361, and broadcasting fallback, it seems)..

The l2/l3 distinction in ipvlan is also very interesting. The L3 mode
solves some of the security type issues. What do you think Haggi?

Is there any chance standard things like ipvlan and macvlan could be
used with rdma-cm if their master devices are IPoIB? Are we even on
the right path to do that someday? Is that the plan for roce?

Any thoughts on the idea we still need ipoib same-guid children if
ipvlan is available?

Jason
--
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