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

protect scp_rqbd_idle list operations in ptlrpc_service_purge_all()

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • Lustre 2.17.0
    • Lustre 2.15.5
    • 3
    • 9223372036854775807

    Description

      There are evidences that list entry taken from scp_rqbd_idle in ptlrpc_service_purge_all() is used then being freed. From code that entry is taken from the list without any protection, so that is possible place when it is being freed at the same time.

      I wasn't able to reproduce that but it seems that is only place where it can happen and solution would be just take the same spinlock svcpt->scp_lock which is used in all other place where these rqbd_list linkage is being used

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. LU-17946 sanity test_818: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! umount

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

          Bug - A problem which impairs or prevents the functions of the product. LU-17946 sanity test_818: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! umount

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

          Activity

            People

              tappro Mikhail Pershin
              tappro Mikhail Pershin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: