From 0ff5c456cb1ad38c3300a214799478101a3540a6 Mon Sep 17 00:00:00 2001 From: Michael Brown Date: Sun, 9 Aug 2009 21:00:48 +0100 Subject: [infiniband] Disambiguate CM connection rejection reasons There is diagnostic value in being able to disambiguate between the various reasons why an IB CM has rejected a connection attempt. In particular, reason 8 "invalid service ID" can be used to identify an incorrect SRP service_id root-path component, and reason 28 "consumer reject" corresponds to a genuine SRP login rejection IU, which can be passed up to the SRP layer. For rejection reasons other than "consumer reject", we should not pass through the private data, since it is most likely generated by the CM without any protocol-specific knowledge. --- src/include/gpxe/ib_mad.h | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/include') diff --git a/src/include/gpxe/ib_mad.h b/src/include/gpxe/ib_mad.h index 54d0a2af..8b497183 100644 --- a/src/include/gpxe/ib_mad.h +++ b/src/include/gpxe/ib_mad.h @@ -402,6 +402,11 @@ struct ib_cm_connect_reject { uint8_t private_data[148]; } __attribute__ (( packed )); +/** CM rejection reasons */ +#define IB_CM_REJECT_BAD_SERVICE_ID 8 +#define IB_CM_REJECT_STALE_CONN 10 +#define IB_CM_REJECT_CONSUMER 28 + /** A communication management connection reply * * Defined in section 12.6.8 of the IBA. -- cgit