linux-kernel - Re: [PATCH 3/3 v3] mm/vmalloc: Cache the vmalloc memory info

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: <87h9npwtx3.fsf@rasmusvillemoes.dk>
Date:	Sun, 23 Aug 2015 23:56:24 +0200
From:	Rasmus Villemoes <linux@...musvillemoes.dk>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	George Spelvin <linux@...izon.com>, dave@...1.net,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	peterz@...radead.org, riel@...hat.com, rientjes@...gle.com,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH 3/3 v3] mm/vmalloc: Cache the vmalloc memory info

I was curious why these fields were ever added to /proc/meminfo, and dug
up this:

commit d262ee3ee6ba4f5f6125571d93d9d63191d2ef76
Author: Andrew Morton <akpm@...eo.com>
Date:   Sat Apr 12 12:59:04 2003 -0700

    [PATCH] vmalloc stats in /proc/meminfo
    
    From: Matt Porter <porter@....net>
    
    There was a thread a while back on lkml where Dave Hansen proposed this
    simple vmalloc usage reporting patch.  The thread pretty much died out as
    most people seemed focused on what VM loading type bugs it could solve.  I
    had posted that this type of information was really valuable in debugging
    embedded Linux board ports.  A common example is where people do arch
    specific setup that limits there vmalloc space and then they find modules
    won't load.  ;) Having the Vmalloc* info readily available is real useful in
    helping folks to fix their kernel ports.

That thread is at <http://thread.gmane.org/gmane.linux.kernel/53360>.

[Maybe one could just remove the fields and see if anybody actually
notices/cares any longer. Or, if they are only used by kernel
developers, put them in their own file.]

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