[openib-general] Re: Bug in recv_handler() -sa_query.c file?

Pradeep Satyanarayana pradeep at us.ibm.com
Tue Oct 18 11:46:58 PDT 2005





Good point about the endianness bug. That could be something.
I got 0x600 for status (printed as %x). We have a Topspin switch which runs
the SM

Pradeep
pradeep at us.ibm.com

Roland Dreier <rolandd at cisco.com> wrote on 10/18/2005 11:11:46 AM:

>     Pradeep> Now mad_hdr.status field is declared as __be16. So,
>     Pradeep> should the check be
>
>     Pradeep> (mad_recv_wc->recv_buf.mad->mad_hdr.status & 0xff)
>
>     Pradeep> before we return EINVAL?
>
> I don't see why.  For one thing, that would be an endianness bug,
> since as you say, the status field is in big-endian order, so the test
> would be different depending on whether the host is big- or
little-endian.
>
> Also, all 16 bits of the status field should be zero if the request
> succeeds.  What value do you see in the status field in the failed
> response?  What SM are you using?
>
>  - R.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20051018/a6062c9d/attachment.html>


More information about the general mailing list