Bug #55254: kclient: fix statx AT_STATX_DONT_SYNC vs AT_STATX_FORCE_SYNC check - Linux kernel client - Ceph

Actions

Copy link

Bug #55254

closed

kclient: fix statx AT_STATX_DONT_SYNC vs AT_STATX_FORCE_SYNC check

Added by Xiubo Li about 2 years ago. Updated about 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Xiubo Li

Category:

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

kcephfs

Crash signature (v1):

Crash signature (v2):

Description

From the posix and the initial statx supporting commit comments,
the AT_STATX_DONT_SYNC is a lightweight stat flag and the
AT_STATX_FORCE_SYNC is a heaverweight one. And also checked all
the other current usage about these two flags they are all doing
the same, that is only when the AT_STATX_FORCE_SYNC is not set
and the AT_STATX_DONT_SYNC is set will they skip sync retriving
the attributes from storage.

More detail please see https://lore.kernel.org/all/147938970382.13574.11581172952175034619.stgit@warthog.procyon.org.uk/.

Related issues 1 (0 open — 1 closed)