linux-kernel - Re: v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1 sticks-and-crashs)

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]

Date:	Mon, 09 Apr 2012 22:13:13 -0400
From:	"werner" <w.landgraf@...ru>
To:	Rik van Riel <riel@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
	Oleg Nesterov <oleg@...hat.com>,
	Rabin Vincent <rabin.vincent@...ricsson.com>,
	Christian Bejram <christian.bejram@...ricsson.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Anton Vorontsov <anton.vorontsov@...aro.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	stable@...r.kernel.org, rientjes@...gle.com
Subject: Re: v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1
 sticks-and-crashs)

Rik van Riel :
To avoid misunderstandings, that improvement is WITH / 
INCLUDING the patch suggested by D.R and L.T., namely: 
 put + free_task(task); after line 78 in subroutine 
lowmemorykiller.c   .  At least phenomenologically, it 
looks that it resolved the problem
I dont understanding so much about programming and about 
the problem (and "android" is neither running on my own 
computer nor on my coffee-machine, but I enable everything 
just because I don't know what hardware have the people 
which use my distro and compiled kernels) so that I don't 
understand all details of the discusion,  but if people 
come to an agreement what I could test further, one can 
mail it me and explain it me slowly, then I test it out.
wl

==========

On Mon, 09 Apr 2012 21:51:58 -0400
  Rik van Riel <riel@...hat.com> wrote:
> On 04/09/2012 09:52 PM, werner wrote:
>> At least until now, and also tested hard by starting and 
>>stopping
>> several memory-consuming operations, I'm happy to can 
>>inform that the
>> computer didnt yet crash again, and that also 
>>slownessnesses what I
>> observed under 3.3 (but without crashs) don't occur
> 
> That could be due to a few VM patches which I wrote, 
>that
> went in through -mm.
> 
> I am very interested in whether people do find a way to
> break the VM with those patches, in ways that used to 
>work
> before.
> 
> If you find any, please let me know so I can fix them
> before the 3.4 kernel comes out.
> 
> If everything you try works better than before, I'm not
> going to complain about good news :)
> 
> -- 
> All rights reversed
> 
> 

"werner" <w.landgraf@...ru>
---
Professional hosting for everyone - http://www.host.ru
--
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/