Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-17632

o2iblnd: graceful handling of unexpected CM_EVENT_CONNECT_ERROR

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.16.0
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      There were examples in the field with RoCE setups which demonstrate that RDMA_CM_EVENT_CONNECT_ERROR may be received when connection is neither in IBLND_CONN_ACTIVE_CONNECT nor IBLND_CONN_PASSIVE_WAIT state

      This causes the assertion in kiblnd_cm_callback() to fail:

       ASSERTION( conn->ibc_state == 1 || conn->ibc_state == 2 )

      It is proposed to handle this in a more gracious manner:  report the event as unexpected and allow the flow to continue. If there are indeed issues on the connection, it is expected to report transaction errors and get cleaned up without crashing the whole system.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-18260 o2iblnd: graceful handling of unexpected RDMA_CM_EVENT_REJECTED

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-17480 lustre_rmmod hangs if a lnet route is down

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              ssmirnov Serguei Smirnov
              ssmirnov Serguei Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: