On Thu, 14 Oct 2021 at 19:53:14 +0200, Marc Lehmann wrote: > On Tue, Oct 12, 2021 at 12:33:32AM +0200, Guilhem Moulin <guil...@debian.org> > wrote: >> Could you please share the memory cost of the PBKDF, > > I wouldn't know how to do that.
`cryptsetup luksDump` >> of `free` just before running cryptsetup? That would help us trying to >> reproduce this and forward the issue upstream. I tried to reproduce >> this but only managed to trigger the OOM killer. > > Not sure what this extra information has to do with the problem I reported Which is why I'm saying, I tried to reproduce this and failed. >> Also did you run luksFormat on that same machine (and didn't remove >> memory sticks afterwards)? > > There was _significantly_ less memory in the machine at the time of the > problem. Unrelated to this issue, it's best to run `cryptsetup luksChangeKey` after hardware changes to use adequate PBKDF parameters. > I think you are likely confused about the nature of the problem I reported > - the problem is not that cryptsetup used too much memory. The problem > is that it only reported it when using an extra option, as opposed to > reporting it when it hit the issue. > > cryptsetup was not killed by the oom killer, so it should have had no > problems reporting the result of some failed allocation. Got that. And again I believe this is https://gitlab.com/cryptsetup/cryptsetup/-/issues/488 . Are you really running 2:2.3.5-1 on the affected system? -- Guilhem.
signature.asc
Description: PGP signature