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: <470B8D04.30401@opengridcomputing.com>
Date:	Tue, 09 Oct 2007 09:15:32 -0500
From:	Steve Wise <swise@...ngridcomputing.com>
To:	Roland Dreier <rdreier@...co.com>
CC:	general@...ts.openfabrics.org, linux-kernel@...r.kernel.org
Subject: Re: [ofa-general] Updated InfiniBand/RDMA merge plans for 2.6.24



Roland Dreier wrote:
>  > No mention about the iwarp port space issue?
> 
> I don't think we're at a stage where I'm prepared to merge something--
> we all agree the latest patch has serious drawbacks, and it commits us
> to a suboptimal interface that is userspace-visible.
> 

Fair enough.

>  > I'm at a loss as to how to proceed.
> 
> Could we try to do some cleanups to the net core to make the alias
> stuff less painful?  eg is there any sane way to make it possible for
> a device that creates 'eth0' to also create an 'iw0' alias without an
> assigning an address?
> 

Well, "alias" interfaces really don't exist.  ethX:iw is really just 
adding a address record (struct in_ifaddr) to ethX.  So in the current 
core design, adding an alias without an address is really adding the 
alias with address 0.0.0.0.  And I think the core net code assumes if an 
in_ifaddr struct exists for a device, then its IP address is indeed valid.

So I think the changes wouldn't be small to enhance the design to add a 
concept of an alias interface.

I'll look into this more though.

Steve.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ