[question] user keyring still linked to root keyring after fscrypt purge command

[ghost]

I noticed that fscrypt purge correctly clear user keyring but it keeps it linked to root keyring

Before user unlocks encrypted directory:

# keyctl show
Session Keyring
 500577725 --alswrv      0     0  keyring: _ses
 749555953 --alswrv      0 65534   \_ keyring: _uid.0

After user unlocks encrypted directory:

# keyctl show
Session Keyring
 500577725 --alswrv      0     0  keyring: _ses
 749555953 --alswrv      0 65534   \_ keyring: _uid.0
 173465956 ---lswrv   1001 65534       \_ keyring: _uid.1001
 462364131 --alsw-v   1001  1001           \_ logon: ext4:949471831dcf55cf

After fscrypt purge / --force --user=user1

# keyctl show
Session Keyring
 500577725 --alswrv      0     0  keyring: _ses
 749555953 --alswrv      0 65534   \_ keyring: _uid.0
 173465956 ---lswrv   1001 65534       \_ keyring: _uid.1001

Is it correct behavior? I think it should be back to clean state which means unlinking user keyring from root keyring.

[ebiggers]

I'm considering this to be WONTFIX, since fscrypt using the user keyrings is deprecated. New systems set up with a recent version of fscrypt and a recent kernel use filesystem-level keyrings instead of the user keyrings; on such systems, fscrypt won't link user keyrings into root's user keyring anymore. Also this question never really made sense in the first place given that fscrypt purge is a per-filesystem thing, but the user keyrings are a per-user thing.