[openib-general] [PATCH 2/2] ib_cm: fix REJ due to invalid GID
Arne Redlich
arne.redlich at xiranet.com
Fri Jul 21 00:44:36 PDT 2006
Am Donnerstag, den 20.07.2006, 18:44 +0300 schrieb Michael S. Tsirkin:
> Quoting r. Arne Redlich <arne.redlich at xiranet.com>:
> > Subject: Re: [openib-general] [PATCH 2/2] ib_cm: fix REJ due to invalid GID
> >
> > Am Mittwoch, den 19.07.2006, 20:05 +0300 schrieb Michael S. Tsirkin:
> > > Quoting r. Arne Redlich <arne.redlich at xiranet.com>:
> > > > Subject: Re: [openib-general] [PATCH 2/2] ib_cm: fix REJ due to invalid GID
> > > >
> > > > Am Dienstag, den 18.07.2006, 12:21 -0700 schrieb Sean Hefty:
> > > > > Arne Redlich wrote:
> > > > > > Yep - the Gen1 SRP initiator does. It sends a REQ with an invalid DGID.
> > > > > > If rejected with the correct code (INVALID GID), it will retry after
> > > > > > looking up the GID.
> > > > >
> > > > > Didn't it have a DGID from a path record that it had to get before sending the REQ?
> > > >
> > > > If I'm not completely mistaken, the path lookup is only done after
> > > > receiving an IB_CM_REJ_INVALID_GID. I have no idea why it is done this
> > > > way, though.
> > > >
> > > > Arne
> > >
> > > Er ... how does it send the REQ then?
> >
> > The path record's {D,S}LID (as well as the SGID) are initialized
> > correctly in the 1st REQ.
>
> Sorry for being dense ... Why not the GID then?
I only took a rather superficial look at the code. But since the invalid
GID REJ is treated with such care, I guess it's intentional and not a
bug?
Maybe (one of) the original author(s) is around and can shed some light
into this?
Arne
--
Arne Redlich
Xiranet Communications GmbH
More information about the general
mailing list