Actions
Bug #63722
opencephfs/fuse: renameat2 with flags has wrong semantics
Status:
Pending Backport
Priority:
Normal
Assignee:
Category:
Correctness/Safety
Target version:
% Done:
0%
Source:
Community (dev)
Tags:
backport_processed
Backport:
quincy,reef
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client, ceph-fuse
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Linux renameat2 system call has additional optional flags (RENAME_EXCHANGE, RENAME_NOREPLACE, RENAME_WHITEOUT) which affects the semantics of the rename operations. On the kernel client side, a user call to renameat2 with non-zero flags yields -EINVAL. On the other hand, the ceph-fuse client ignore those flags (when libfuse version >= 3.0) which may end up with rename operation with different semantics then those requested by the user.
Updated by Venky Shankar 5 months ago
- Project changed from Ceph to CephFS
- Assignee set to Shachar Sharon
- Target version set to v19.0.0
- Backport set to quincy,reef
- Component(FS) Client, ceph-fuse added
Updated by Venky Shankar 5 months ago
- Status changed from New to Fix Under Review
- Pull request ID set to 54733
Updated by Venky Shankar 5 months ago
- Category set to Correctness/Safety
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot 5 months ago
- Copied to Backport #63822: reef: cephfs/fuse: renameat2 with flags has wrong semantics added
Updated by Backport Bot 5 months ago
- Copied to Backport #63823: quincy: cephfs/fuse: renameat2 with flags has wrong semantics added
Actions