Actions
Bug #66828
closedmds: cephx path restriction incorrectly rejects snapshots of deleted directory
Status:
Resolved
Priority:
High
Assignee:
Category:
Correctness/Safety
Target version:
% Done:
100%
Source:
Support
Backport:
squid,reef,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
snapshots
Pull request ID:
Tags (freeform):
backport_processed
Merge Commit:
Fixed In:
v19.3.0-4530-g64e2bd347b
Released In:
v20.2.0~2152
Upkeep Timestamp:
2025-11-01T01:27:47+00:00
Description
2024-07-04T02:05:07.884+0000 7f319ce86640 20 Session check_access: [inode 0x10000000002 [2,2] ~mds0/stray2/10000000001/file ...] caller_uid=1141 caller_gid=1141 caller_gid_list=[1000,1141] 2024-07-04T02:05:07.884+0000 7f319ce86640 20 Session check_access path ~mds0/stray2/10000000001/file
Instead of using the stray_prior_path it uses the stray path. This causes a deleted directory tree's files to be inaccessible.
Updated by Patrick Donnelly over 1 year ago
- Status changed from New to Fix Under Review
- Pull request ID set to 58419
Updated by Patrick Donnelly over 1 year ago
- Status changed from Fix Under Review to Pending Backport
Updated by Upkeep Bot over 1 year ago
- Copied to Backport #67749: quincy: mds: cephx path restriction incorrectly rejects snapshots of deleted directory added
Updated by Upkeep Bot over 1 year ago
- Copied to Backport #67750: reef: mds: cephx path restriction incorrectly rejects snapshots of deleted directory added
Updated by Upkeep Bot over 1 year ago
- Copied to Backport #67751: squid: mds: cephx path restriction incorrectly rejects snapshots of deleted directory added
Updated by Konstantin Shalygin about 1 year ago
- Status changed from Pending Backport to Resolved
- % Done changed from 0 to 100
Updated by Upkeep Bot 9 months ago
- Merge Commit set to 64e2bd347b88c8f035f42d3730d832e9ac68db5f
- Fixed In set to v19.3.0-4530-g64e2bd347b88
- Upkeep Timestamp set to 2025-06-25T23:05:18
Updated by Upkeep Bot 9 months ago
- Fixed In changed from v19.3.0-4530-g64e2bd347b88 to v19.3.0-4530-g64e2bd347b8
- Upkeep Timestamp changed from 2025-06-25T23:05:18 to 2025-07-08T18:29:46+00:00
Updated by Upkeep Bot 8 months ago
- Fixed In changed from v19.3.0-4530-g64e2bd347b8 to v19.3.0-4530-g64e2bd347b
- Upkeep Timestamp changed from 2025-07-08T18:29:46+00:00 to 2025-07-14T17:10:28+00:00
Updated by Upkeep Bot 5 months ago
- Released In set to v20.2.0~2152
- Upkeep Timestamp changed from 2025-07-14T17:10:28+00:00 to 2025-11-01T01:27:47+00:00
Actions