Control: tag -1 confirmed

Guilhem Moulin <guil...@debian.org> (2023-04-25):
> It was discovered that the upstream patch mitigating #1028250 was
> incomplete: `cryptsetup luksFormat` still caused OOM on some memory
> constrained systems.  This was fixed upstream in a new MR, which is
> backported in sid in 2:2.6.1-4.
> 
> Unfortunately the version (like -3) is barred from entering testing due
> to a dependency on libargon2-1-udeb ≥0~20190702+dfsg, hence the request
> to go via t-p-u instead.  See https://bugs.debian.org/1032235#107 .
> 
> [ Impact ]
> 
> Running `cryptsetup luksFormat` might OOM on systems with ≤1G RAM when
> the memory pressure exceeds 50%.  Concretely, that means one might not
> be able to relying use the “encrypted LVM” partitioning scheme from the
> graphical installer on such systems.
> 
> [ Tests ]
> 
>  * DEP-8 tests, incl. full upstream test suite and cryptroot tests.
>  * Comparison of memory costs between releases from d-i depending on the
>    amount of RAM: https://bugs.debian.org/1028250#78 .
> 
> [ Risks ]
> 
> The change only affets systems with <2G RAM, and among those only the
> ones without swap area.  That includes low-memory rescue systems and
> d-i, but not “normal systems”.

The backporting from unstable looks sane to me, please go ahead.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature

Reply via email to