linux-kernel - RE: VM: killing process - How to identify the problem

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] [day] [month] [year] [list]

Message-ID: <87A697E50899F541B77272C331CEB7440174624C@exchange.Q-DOMAIN>
Date:	Wed, 21 May 2008 12:30:10 -0700
From:	"Mudeem Siddiqui" <mudeem@...rtics.com>
To:	"Jiri Slaby" <jirislaby@...il.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: RE: VM: killing process - How to identify the problem

>Just curious, is is a typo?

I would say is is is a typo :)

>> 
>> __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.

Can this condition arise due to some other reason other than memory
leak. E.g the way the paging is being done etc because the application
calls malloc only once when it starts. I have been struggling with this
for quite a while, how would you recommend I should try to solve this?

Thanks
--
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/