From: Steve Wise <swise@opengridcomputing.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
general@lists.openfabrics.org
Subject: Re: [ofa-general] [PATCH 2.6.25] RDMA/cxgb3: Fail loopback connections.
Date: Tue, 12 Feb 2008 19:41:53 -0600 [thread overview]
Message-ID: <47B24AE1.7040709@opengridcomputing.com> (raw)
In-Reply-To: <adafxvxvgz3.fsf@cisco.com>
Roland Dreier wrote:
> applied, although:
>
> > +static void is_loopback_dst(struct iw_cm_id *cm_id)
> > +{
> > + struct net_device *dev;
> > +
> > + dev = ip_dev_find(&init_net, cm_id->remote_addr.sin_addr.s_addr);
> > + if (!dev)
> > + return 0;
> > + dev_put(dev);
> > + return 1;
> > +}
>
> is there any way this could trigger when it should, like if I'm trying
> to make a connection from one local device to a different local device
> (which should work fine)?
>
As far as I can tell, if the app does a rdma_resolve_addr() on the dst
addr (which is a local address), then the routing lookup will find the
local interface with that dst addr, and that device will be used for the
connect. IE src and dst devices are the same.
Maybe if the app does an explicit bind to the addr on one device, then
connects to the addr on the other device. But that's not gonna work
either, I think. I still think it will resolve to one device and that
device cannot do loopback...
Steve.
next prev parent reply other threads:[~2008-02-13 1:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 22:09 [PATCH 2.6.25] RDMA/cxgb3: Fail loopback connections Steve Wise
2008-02-13 0:26 ` [ofa-general] " Roland Dreier
2008-02-13 1:41 ` Steve Wise [this message]
2008-02-13 9:18 ` [ofa-general] [PATCH 2.6.25] RDMA/cxgb3: Fail loopbackconnections Diego Guella
2008-02-13 15:46 ` Roland Dreier
2008-02-13 15:47 ` Steve Wise
2008-02-13 15:49 ` Roland Dreier
2008-02-13 15:51 ` Steve Wise
2008-02-13 16:03 ` Steve Wise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47B24AE1.7040709@opengridcomputing.com \
--to=swise@opengridcomputing.com \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox