[LU-9033] Don't zero timestamps in lock blocking callback

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.10.0
• Severity: 3
• Assignee: Niu Yawei (Inactive)
• Reporter: Niu Yawei (Inactive)

Description

In ll_md_blocking_ast(), we zero all timestamps to avoid these 'leftovers' interfering the new timestamps from MDS, especially when the timestamps are set back by other clients. It's not quite right to change timestamps in this way, because:

1. The pending lock can be matched by getattr, so these zero timestamps can be fetched by application in a small race window.

2. It doesn't make sense to zero the mtime and ctime, because we always use the newest ctime and mtime from MDS when do attributes merge, the 'leftovers' won't interfere new timestamps set by other clients.

Comments

[Peter Jones]

Landed for 2.10

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/24984/
Subject: LU-9033 llite: don't zero timestamps internally
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 8718346e06cf2e17447dd3e3dc4e45b66d945aaf

[Gerrit Updater]

Niu Yawei ([e-mail]) uploaded a new patch: https://review.whamcloud.com/24984
Subject: LU-9033 llite: don't zero timestamps internally
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 05a3ee7523d7bcdf7e1897669c4df2c9160c11ca