Problems using non-libc memory allocators
Hey I was trying to use dovecot2 with a not libc based memory allocation such as scudo or graphene-hardened or graphene-hardened-light but ran into the issues I described in
https://github.com/NixOS/nixpkgs/issues/313721
I just wanted to mention this here as well as this behavior may suggest a flaw in the memory allocation mechanism of dovecot2/anvil. I haven't yet found the time to check the underlaying issue
as I'm quite busy rn. So I thought id just mention what I came across in case this is actually unexpected or potentially even security relevant mis/behavior.
On 22/05/2024 19:38 EEST bl0v3 via dovecot dovecot@dovecot.org wrote:
Hey I was trying to use dovecot2 with a not libc based memory allocation such as scudo or graphene-hardened or graphene-hardened-light but ran into the issues I described in
https://github.com/NixOS/nixpkgs/issues/313721
I just wanted to mention this here as well as this behavior may suggest a flaw in the memory allocation mechanism of dovecot2/anvil. I haven't yet found the time to check the underlaying issue
as I'm quite busy rn. So I thought id just mention what I came across in case this is actually unexpected or potentially even security relevant mis/behavior.
Hi!
Looking at your issue it seems that graphene ones don't even make it to Dovecot code.
Perhaps you should experiment with default_vsz_limit or per-process vsz_limit, maybe the default limit is too low for these allocators?
Aki
participants (2)
-
Aki Tuomi
-
bl0v3