Lennart Poettering
Lennart Poettering
lgtm, just one trivial nitpicj.
the cryptsetup loop was recently reworked, can you make sure this works as intended still?
also do "systemd-analyze --user log-level debug", and then reproduce the issue and provide logs around the issue from journalctl here, otherwise this is not actionable to us.
Closing due to lack of response.
We only track issues in the most current two systemd versions here. 215 is waaaay too old (almost 4y), the current version is 238 after all. The issue submission form...
do you find an "Failed to drop caches, ignoring" log message in your journal when you fully log out? do you have user lingering disabled?
Hmm, so your kernel even acks the drop caches call in the logs: ``` May 24 14:02:26 unstable-amd64 kernel: systemd-homewor (666): drop_caches: 2 ``` You are saying the files/dirs are...
@dkg are you sure that the key that's kept around is actually the fscrypt key? i.e. see /proc/keys for that. It's a frcikin mess to parse, but that's where you...
(but either way, if this actually *is* the fscrypt key that sticks around, then we should find a way to kill it, but that should be a separate issue)
btw, the reason we issued drop_caches with a level of 2 instead of 3 was because that's what fscrypt docs say: https://www.kernel.org/doc/html/v4.18/filesystems/fscrypt.html#online-attacks