On Mon, 2021-04-19 at 18:24 +0100, Daniel P. Berrangé wrote:
> On Mon, Apr 19, 2021 at 01:12:07PM -0400, Simo Sorce wrote:
> > On Mon, 2021-04-19 at 12:02 +0100, Richard W.M. Jones wrote:
> > > On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote:
> > > > 2. LUKS2 prefers Argon2 as the key d
On Mon, Apr 19, 2021 at 01:12:07PM -0400, Simo Sorce wrote:
> On Mon, 2021-04-19 at 12:02 +0100, Richard W.M. Jones wrote:
> > On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote:
> > > 2. LUKS2 prefers Argon2 as the key derivation function, designed to
> > > use a lot of memory. kdump is e
On Mon, Apr 19, 2021 at 01:12:07PM -0400, Simo Sorce wrote:
> On Mon, 2021-04-19 at 12:02 +0100, Richard W.M. Jones wrote:
> > On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote:
> > > 2. LUKS2 prefers Argon2 as the key derivation function, designed to
> > > use a lot of memory. kdump is e
On Mon, 2021-04-19 at 12:02 +0100, Richard W.M. Jones wrote:
> On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote:
> > 2. LUKS2 prefers Argon2 as the key derivation function, designed to
> > use a lot of memory. kdump is expected to use a minimal amount of
> > memory. Users will have to re
On 19.04.2021 13:02, Richard W.M. Jones wrote:
I'm just going to sympathise with you rather than provide a good
answer here ... We had the same problem in libguestfs where Argon2
used too much memory for our small appliance when opening LUKS2 disks.
We had to simply increase the amount of memory
On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote:
> 2. LUKS2 prefers Argon2 as the key derivation function, designed to
> use a lot of memory. kdump is expected to use a minimal amount of
> memory. Users will have to reserve a huge amount of memory for kdump
> to work (eg. 1G reserve for
