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, 21 Oct 2011 08:36:36 +0200
From:	Philipp Herz - Profihost AG <p.herz@...fihost.ag>
To:	Valdis.Kletnieks@...edu
CC:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: Vanilla-Kernel 3 - page allocation failure

> On Tue, 18 Oct 2011 08:51:54 PDT, Andi Kleen said:
>> Philipp Herz - Profihost AG<p.herz@...fihost.ag>  writes:
>>
>>> After updating kernel (x86_64) to stable version 3 there are a few
>>> messages appearing in the kernel log such as
>>>
>>> kworker/0:1: page allocation failure: order:1, mode:0x20
>>> mysql: page allocation failure: order:1, mode:0x20
>>> php5: page allocation failure: order:1, mode:0x20
>>
>> You just ran out of memory.
>
> I read it as "Why is this happening when the previous kernel didn't have
> this issue?", which is a *much* more complicated question...

Exactly, that was the intention of my post.

It would me nice to know, if these messages do require to focus on 
memory statitics?

Looking at our monitoring data, the system does have enough memory 
available.

How do processes get effected, when they are running into situations 
where kernel memory manager tells them about "page allocation failure"?

Is it just meant to be a warning/debugging message new to current kernel 
version 3?

How can we solve the situation? Getting rid of these message, by

- just suppressing
- increasing system's memory
- change kernel and/or kernel runtime config

?

Kind regards,
Philipp
--
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