linux-kernel - Re: Page allocation failures in guest

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]

Message-ID: <4A827EE9.7090102@redhat.com>
Date:	Wed, 12 Aug 2009 11:35:53 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Pierre Ossman <drzeus-list@...eus.cx>
CC:	Rusty Russell <rusty@...tcorp.com.au>,
	Minchan Kim <minchan.kim@...il.com>, kvm@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
	Wu Fengguang <fengguang.wu@...el.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Rik van Riel <riel@...hat.com>
Subject: Re: Page allocation failures in guest

On 08/12/2009 11:22 AM, Pierre Ossman wrote:
>>
>>> Will it still trigger the OOM killer with this patch, or will things
>>> behave slightly more gracefully?
>>>
>>>        
>> I don't think you mentioned the OOM killer in your original report?  Did
>> it trigger?
>>
>>      
>
> I might have things backwards here, but I though the OOM killer started
> doing its dirty business once you got that memory allocation failure
> dump.
>    

I don't think the oom killer should trigger on GFP_ATOMIC failures, but 
don't know for sure.  If you don't have a trace saying it picked a task 
to kill, it probably didn't.

-- 
error compiling committee.c: too many arguments to function

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