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.
> 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
- the problem is that the oom error is not reported unless -v is used,
which has nothing to do with the oom killer or how much memory was needed
- cryptsetup surely had reasons to use a lot of memory, but it should
report an error if it can, as opposed to silently fail to do its job.
> 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.
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.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
