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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 21 Dec 2006 06:26:43 +0100
From:	Willy Tarreau <w@....eu>
To:	rrcwjpgr <rrcwjpgr@...shmail.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.4.28: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) ?

Hello,

On Mon, Dec 18, 2006 at 11:32:43AM +0100, rrcwjpgr wrote:
> Hello,
> 
> first thanks for your great support on the Linux kernel.
> I have a problem with kernel 2.4.28 and maybe somebody has an idea about my problem. When I type dmesg, I get this error messages:
> __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> VM: killing process python
> 
> For any kind of reason a python script is killed.
> What this kind of error message means?
> Is this the memory killer?

exactly !

> This would mean that maybe I have a memory leak in the python script?

Generally, when you get this on scripts written in such "high level"
languages, this is because you fill variables with a file which does
not fit into memory. I have often seen this in people's perl scripts,
and sometimes even in shell scripts. Eg: 

  count=$(cat file)

Where file is unexpectedly big, or even a link to /dev/zero. This is
an excellent OOM trigger.

You can use ulimit (man bash) to limit the amount of memory your script
can use. At least it will not make the system go ill.

Regards,
Willy

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ