| 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
| ||
|
Date: Wed, 21 May 2008 09:44:47 +0200 From: Jiri Slaby <jirislaby@...il.com> To: Mudeem Siddiqui <mudeem@...rtics.com> CC: linux-kernel@...r.kernel.org Subject: Re: VM: killing process - How to identify the problem On 05/20/2008 11:10 PM, Mudeem Siddiqui wrote: > Hi all, > > I have linux 2.4.25 on a mips processor. Other than my application, the Just curious, is is a typo? > other processes that are running on the system are udhcpd, dhcpd, > mini_dns etc. The applicaiton is quite memory intensive, it has > allocated 5 MB of a buffer which acts as a queue and the applicaiton > queues and de-queues packets in the queue at frequents intervals. The > memory for this buffer is allocated just once when the application > starts at the time of boot. So I would assume that there would be quite > a lot of paging going on. > > The issue is that randomly the application gets killed, there is no > segmnetation fault or anything and if I look at /var/log/messages I see > quite a lot of > > __alloc_pages: 0-order allocation failed > __alloc_pages: 0-order allocation failed > __alloc_pages: 0-order allocation failed > > > and then > > VM: killing process Caused by out of memory, a page fault couldn't be serviced due to memory exhaustion. See arch/mips/mm/fault.c. -- 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/
Powered by blists - more mailing lists