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

rename may miss revoking LOOKUP lock to cause stale dentry on client

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • Lustre 2.10.0, Lustre 2.12.0, Lustre 2.13.0
    • Lustre 2.14.0, Lustre 2.12.6
    • 3
    • 9223372036854775807

    Description

      In rename, all objects involved but target may be remote, i.e. source, source parent, target parent may be remote object, herein to know whether source is a remote object on source parent, we need to compare which MDT they are located.

      In mdt_getattr_name_lock(), if name is NULL, the LOOKUP lock can't be returned to client, because this object may be a remote object under its parent, and the remote LOOKUP lock is on the MDT where its parent is located.

      Attachments

        Issue Links

          Activity

            People

              laisiyao Lai Siyao
              laisiyao Lai Siyao
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: