Description
We could try to make the Lustre GSS code more robust to issues with the session keyring, such as when it is revoked, unlinked, or unavailable. We depend on the kernel implementation of request_key for that matter, so we need to implement workarounds.
One other possibility could be to link the keyring used by Lustre (user keyring for regular users for now, but could be a Lustre specific keyring in the future) to the thread keyring. The request key procedure as implemented in the kernel searches for keys in the thread keyring before the session keyring. So that would be a way to workaround issues that may happen with an incorrect session keyring.