Actions
Bug #64542
openDifference in error code returned while removing system xattrs using removexattr()
Status:
Pending Backport
Priority:
Normal
Assignee:
Category:
Correctness/Safety
Target version:
% Done:
0%
Description
During removexattr() operation for those xattrs from "system." namespace, kernel client returns ENOTSUP in early stages whereas libcephfs allows it to pass through reporting the status accordingly as ENODATA among others. In fact it is the expectation as seen with local file systems like xfs, ext4 etc. There is also the special case with POSIX ACL xattrs where a removal attempt for 'system.posix_acl_access' or 'system.posix_acl_default' is always expected to complete successfully irrespective of whether those xattrs are present on files/directories. libcephfs fails to meet these expectations causing unexpected issues with test suites from integrations like Samba.
Updated by Venky Shankar 3 months ago
- Status changed from New to Pending Backport
- Assignee set to Anoop C S
- Target version changed from v19.0.0 to v20.0.0
- Backport changed from quincy, reef to quincy,reef,squid
Updated by Backport Bot 3 months ago
- Copied to Backport #64564: quincy: Difference in error code returned while removing system xattrs using removexattr() added
Updated by Backport Bot 3 months ago
- Copied to Backport #64565: reef: Difference in error code returned while removing system xattrs using removexattr() added
Updated by Backport Bot 3 months ago
- Copied to Backport #64566: squid: Difference in error code returned while removing system xattrs using removexattr() added
Actions