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  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]
Date:	Wed, 05 Sep 2007 08:18:00 -0700
From:	Roland Dreier <>
To:	Steve Wise <>
Subject: Re: [PATCH RFC] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts with the host stack.

 > > What's wrong with my suggestion of having the iwarp driver create an
 > > "iwX" interface to go with the normal "ethX" interface?  It seems
 > > simpler to me, and there's a somewhat similar precedent with how
 > > mac80211 devices create both wlan0 and wmaster0 interfaces.
 > >  - R.
 > It seemed much more painful for me to implement. :-)
 > I'll look into this, but I think for this to be done, the changes must
 > be in the cxgb3 driver, not the rdma driver, because the guts of the
 > netdev struct are all private to cxgb3.  Remember that this interface
 > needs to still do non TCP traffic (like ARP and UDP)...
 > Maybe you have something in mind here that I'm not thinking about?

No, I was just spouting off.

But the whole "create a magic alias" seems kind of unfriendly to the
user.  Maybe as you said, the cxgb3 net driver could create the alias
for the iw_cxgb3 driver?

 - R.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists