Project

General

Profile

Bug #52982

client: Inode::hold_caps_until should be a time from a monotonic clock

Added by Patrick Donnelly about 1 year ago. Updated 5 months ago.

Status:
Resolved
Priority:
High
Category:
Correctness/Safety
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
quincy, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client
Labels (FS):
task(easy), task(intern)
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The use of the real clock is vulnerable to system clock changes that could prevent release of any caps.

Use ceph::coarse_mono_clock and ceph::coarse_mono_time. See src/mds for uses.


Related issues

Copied to CephFS - Backport #55936: quincy: client: Inode::hold_caps_until should be a time from a monotonic clock Resolved
Copied to CephFS - Backport #55937: pacific: client: Inode::hold_caps_until should be a time from a monotonic clock Resolved

History

#1 Updated by Neeraj Pratap Singh about 1 year ago

  • Status changed from New to In Progress

#2 Updated by Venky Shankar 10 months ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 44247

#3 Updated by Venky Shankar 10 months ago

  • Backport changed from pacific to pacific,quincy

#4 Updated by Venky Shankar 6 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Target version changed from v17.0.0 to v18.0.0
  • Backport changed from pacific,quincy to quincy, pacific

#5 Updated by Backport Bot 6 months ago

  • Copied to Backport #55936: quincy: client: Inode::hold_caps_until should be a time from a monotonic clock added

#6 Updated by Backport Bot 6 months ago

  • Copied to Backport #55937: pacific: client: Inode::hold_caps_until should be a time from a monotonic clock added

#7 Updated by Neeraj Pratap Singh 5 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF