Bug #74934: client: Error listing encrypted case-insensitive directory contents - CephFS - Ceph

Actions

Copy link

Bug #74934

closed

client: Error listing encrypted case-insensitive directory contents

Added by Christopher Hoffman about 1 month ago. Updated 4 days ago.

Status:

Resolved

Priority:

Normal

Assignee:

Christopher Hoffman

Category:

Correctness/Safety

Target version:

Ceph - v21.0.0

% Done:

Source:

Development

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Component(FS):

Client

Labels (FS):

Pull request ID:

67377

Tags (freeform):

Merge Commit:

1b2dbcf2ced9df908ba0ac7b48eb1c02bcde3357

Fixed In:

v20.3.0-6151-g1b2dbcf2ce

Released In:

Upkeep Timestamp:

2026-03-17T10:09:25+00:00

Description

On a case insensitive subvolume (casesensitive=0) that is fscrypt encrypted, listing directory contents doesn’t produce valid output.

$ echo filea > filea
$ ls
ls: cannot access ''$'\250''vSt'$'\221''0α'$'\022\253\367'']'$'\207\027\r''0S'$'\273\357\037\253''Kwon'$'\242\217''߫'$'\231\203''%'$'\253\024\233\004\212''3'$'\250\214\260\207': Permission denied
''$'\250''vSt'$'\221''0α'$'\022\253\367'']'$'\207\027\r''0S'$'\273\357\037\253''Kwon'$'\242\217''߫'$'\231\203''%'$'\253\024\233\004\212''3'$'\250\214\260\207'

But other commands using the file name work as expected:

$ cat filea
filea

Actions

Copy link

Updated by Christopher Hoffman about 1 month ago

This only affects shorter names (ie the ones that aren't trunc'd + hashed).

The case sensitive feature requires a non-folded/non-normalized version of the file name to be stored and we do that in alternate_name. Currently, the code in the case sensitive case will set alternate_name in shorter name case to the enc_name [1]. This version of the enc_name is armored or b64 encoded. When decrypting a file name, a raw ciphertext is required.

1- https://github.com/ceph/ceph/blob/9b5d5f41beea3a7a947711399ea3febdb654af4d/src/client/Client.cc#L1433

Actions

Copy link