linux-kernel - Re: [bug, 4.8] /proc/meminfo: counter values are very wrong

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:	Thu, 4 Aug 2016 13:24:09 +0100
From:	Mel Gorman <mgorman@...hsingularity.net>
To:	Dave Chinner <david@...morbit.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [bug, 4.8] /proc/meminfo: counter values are very wrong

On Thu, Aug 04, 2016 at 03:10:51PM +1000, Dave Chinner wrote:
> Hi folks,
> 
> I just noticed a whacky memory usage profile when running some basic
> IO tests on a current 4.8 tree. It looked like there was a massive
> memory leak from my monitoring graphs - doing buffered IO was
> causing huge amounts of memory to be considered used, but the cache
> size was not increasing.
> 
> Looking at /proc/meminfo:
> 
> $ cat /proc/meminfo
> MemTotal:       16395408 kB
> MemFree:           79424 kB
> MemAvailable:    2497240 kB
> Buffers:            4372 kB
> Cached:           558744 kB
> SwapCached:           48 kB
> Active:          2127212 kB
> Inactive:         100400 kB
> Active(anon):      25348 kB
> Inactive(anon):    79424 kB
> Active(file):    2101864 kB
> Inactive(file):    20976 kB
> Unevictable:    13612980 kB	<<<<<<<<<

This? Very quickly done, no boot testing


diff --git a/fs/proc/meminfo.c b/fs/proc/meminfo.c
index 09e18fdf61e5..b9a8c813e5e6 100644
--- a/fs/proc/meminfo.c
+++ b/fs/proc/meminfo.c
@@ -46,7 +46,7 @@ static int meminfo_proc_show(struct seq_file *m, void *v)
 		cached = 0;
 
 	for (lru = LRU_BASE; lru < NR_LRU_LISTS; lru++)
-		pages[lru] = global_page_state(NR_LRU_BASE + lru);
+		pages[lru] = global_node_page_state(NR_LRU_BASE + lru);
 
 	available = si_mem_available();