chiark / gitweb /
coredump: use realloc() loop instead of malloc(768M)
authorColin Walters <walters@verbum.org>
Wed, 24 Apr 2013 22:19:04 +0000 (18:19 -0400)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Fri, 26 Apr 2013 02:51:31 +0000 (22:51 -0400)
commit910003d022ed299b50ab36228732bb74a23d46ba
treeffe1a8d0850a215e8610666c9687eadea9b2ffcd
parent45df1f2c9a7fee67b37f64ddd00adad5982844fa
coredump: use realloc() loop instead of malloc(768M)

I typically run VMs with 1024MiB allocated; systemd is unable to write
coredumps in this scenario at all because the default kernel
configuration will only overcommit 50% of available RAM.

Avoid this failure by using a realloc() loop.

See: http://lists.freedesktop.org/archives/systemd-devel/2013-April/010709.html
src/journal/coredump.c