Re: process running under Cgroup2 control is OOM'ed if its stdout goes to a file at at tmpfs filesystem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/18/24 7:16 AM, Michal Koutný wrote:
On Sat, Nov 16, 2024 at 05:04:06PM GMT, Toralf Förster <toralf.foerster@xxxxxx> wrote:
I removed any limitation for memory.swap.max and have set memory.max to
the RAM which is needed for the fuzzer.
That should make it, right?
It depends on the workload
With memory.max cgroup OOM is still possible, e.g. if you run out of the
swap space.
I'm not sure that's the answer you expect ¯\_(ツ)_/¯

By default, tmpfs sets the filesystem size limit to half of the available RAM. So unless the the processes in the cgroup also consume a lot of memory besides those for tmpfs, tmpfs write error due to lack of space will happen first before OOM.

Cheers,
Longman





[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [Monitors]

  Powered by Linux