Bug #64542: Difference in error code returned while removing system xattrs using removexattr() - CephFS - Ceph

Actions

Copy link

Bug #64542

open

Difference in error code returned while removing system xattrs using removexattr()

Added by Anoop C S 2 months ago. Updated 2 months ago.

Status:

Pending Backport

Priority:

Normal

Assignee:

Anoop C S

Category:

Correctness/Safety

Target version:

Ceph - v20.0.0

% Done:

Source:

Tags:

backport_processed

Backport:

quincy,reef,squid

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

v18.2.3

ceph-qa-suite:

Component(FS):

libcephfs

Labels (FS):

Pull request ID:

55087

Crash signature (v1):

Crash signature (v2):

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.

Related issues 3 (2 open — 1 closed)