linux-kernel - Re: Out of memory management in embedded systems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Sep 2007 18:59:18 -0700
From:	Daniel Phillips <phillips@...nq.net>
To:	"Daniel Spång" <daniel.spang@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Out of memory management in embedded systems

On Friday 28 September 2007 05:55, Daniel Spång wrote:
> Applications with dynamic input and dynamic memory usage have some
> issues with the current overcommitting kernel. A high memory usage
> situation eventually results in that a process is killed by the OOM
> killer. This is especially evident in swapless embedded systems with
> limited memory and no swap available.

In order to earn the right to fix this problem by inventing new Linux, 
first you need to post a traceback and a cat of /proc/meminfo to prove 
the OOM is a true one, as opposed to a second order effect of a 
writeout lockup.

Regards,

Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/