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:	Mon, 09 Apr 2012 12:33:40 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Sven Joachim <svenjoac@....de>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	werner <w.landgraf@...ru>, David Rientjes <rientjes@...gle.com>,
	Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1 sticks-and-crashs)

On 04/09/2012 12:19 PM, Sven Joachim wrote:
> On 2012-04-09 17:57 +0200, Rik van Riel wrote:
>
>> On 04/09/2012 03:04 AM, Sven Joachim wrote:
>>
>>> While I did not experience any crashes or instabilities (yet?), I'm also
>>> seeing memory leaks.  On a system started this morning, with hardly
>>> anything running:
>>
>>> where I would expect no more than 50 MB used, 400 MB are actually in use:
>>>
>>> ,----
>>> | $ free
>>> |              total       used       free     shared    buffers     cached
>>> | Mem:       3348400    1849712    1498688          0     328960    1119180
>>> | -/+ buffers/cache:     401572    2946828
>>> | Swap:      3719040          0    3719040
>>> `----
>>
>> Do you see any big memory users in /proc/meminfo or in
>> /proc/slabinfo?
>
> Attaching these files, since I can't really make anything out of the
> latter.  Note that I started a few memory hogs (X, Firefox, Emacs with
> Gnus), so overall memory footprint has grown to 768 MB.

Looks like the "missing" 400MB is all in filesystem caches,
specifically the dentry cache, the ext4 inode cache and
buffer heads.

That is perfectly fine, since those caches will be shrunk
when the system needs memory.

-- 
All rights reversed
--
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