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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <web-723290478@zbackend1.aha.ru>
Date:	Tue, 10 Apr 2012 03:09:45 -0400
From:	"werner" <w.landgraf@...ru>
To:	David Rientjes <rientjes@...gle.com>,
	Colin Cross <ccross@...gle.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Rik van Riel <riel@...hat.com>,
	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
Subject: Re: v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1
 sticks-and-crashs)

After first I tested some hours the 1st,one-line patch by 
D.R., now is ready compiled and started to be tested his 
2nd patch, below.   I see he has it already comitted; it 
would have been better first wait to test it.

The loop suggested below, with this 2nd patch, gives 1560 
kB , compared with 1632 kb after the 1st patch, and 1432 
kB with kernel 3.3  .    On the other hand, 3.3 has 
clearly the same problem (even if not crashing, it's 
becoming often very slow, and then  there's running 
kmemleak, what I have to kill for return to the normal 
speed), but according this 'test' it would be good, so 
that it's questionable if this test is reliable.

As already reported, the 1st patch cured the problem at 
least subjectively.

To see if this 2nd patch is good, I have to wait now some 
hours and observe if the computer becomes slow or even 
crashs


wl


=================================================

On Mon, 9 Apr 2012 17:11:45 -0700 (PDT)
  David Rientjes <rientjes@...gle.com> wrote:
> On Mon, 9 Apr 2012, werner wrote:
> 
>> I continue now testing your first patch a few hours, if 
>>it's good or not.
>> Then, I can make another patch.  So you have still time 
>>to think and put all
>> together
>> what you want to be tested, and mail me that. Also 
>>explain me, if you want
>> other
>> patchs ADDITIONALLY or INSTEAD your first patch -- the 
>>best would be, to send
>> me
>> always accumulating patchs including everything together 
>>to be applied over
>> the
>> 'virgin' 3.4-rcX kernel.
>> For your information, I dont download the whole git, I 
>>download all 3.X.Y-rcZ
>> , and I
>> recompile everything again (patched), instead of 
>>compiling only the patched
>> subroutines.
>> 
> 
> Ok, when you want to test the latest patch, try this:
> 
> - revert back to the vanilla 3.4-rc2 kernel,
> 
> - boot and do this on the command line:
> 
> 	for i in $(seq 1 10000); do sleep 0 & done
> 	grep KernelStack /proc/meminfo
> 
> - record that number,
> 
> - apply the patch at https://lkml.org/lkml/2012/4/9/428,
> 
> - boot and do the same two command lines,
> 
> - compare the number with the previous number from the 
>first boot.
> 
> The number should be much lower after the patch is 
>applied.
> 
> Thanks!
> 
> 

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