linux-kernel - Re: OOM-Killer kills too much with 2.6.32.2

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: <op.u66q2pjuasvm2a@kedge>
Date:	Wed, 27 Jan 2010 10:53:03 +0100
From:	"Roman Jarosz" <kedgedev@...il.com>
To:	"KOSAKI Motohiro" <kosaki.motohiro@...fujitsu.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	"A Rojas" <nqn1976list@...il.com>,
	"Hugh Dickins" <hugh.dickins@...cali.co.uk>,
	"A. Boulan" <arnaud.boulan@...ertysurf.fr>, michael@...nelt.co.at,
	jcnengel@...glemail.com, rientjes@...gle.com, earny@...4u.de,
	"Jesse Barnes" <jbarnes@...tuousgeek.org>,
	"Eric Anholt" <eric@...olt.net>,
	"Chris Wilson" <chris@...is-wilson.co.uk>
Subject: Re: OOM-Killer kills too much with 2.6.32.2

On Wed, 27 Jan 2010 01:14:44 +0100, KOSAKI Motohiro  
<kosaki.motohiro@...fujitsu.com> wrote:

>> > -	mapping_set_gfp_mask(obj->filp->f_path.dentry->d_inode->i_mapping,
>> > -			     GFP_HIGHUSER |
>> > -			     __GFP_COLD |
>> > -			     __GFP_FS |
>> > -			     __GFP_RECLAIMABLE |
>> > -			     __GFP_NORETRY |
>> > -			     __GFP_NOWARN |
>> > -			     __GFP_NOMEMALLOC);
>> > -
>> >  	kref_init(&obj->refcount);
>> >  	kref_init(&obj->handlecount);
>> >  	obj->size = size;
>>
>> I've applied this patch and I'm testing it right now.
>> Btw. what this patch will do from user(my) point of view?
>
> OOM Killer disappear :)

Looks like the patch works... no oom kills so far.

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/