[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1317413714.16137.666.camel@nimitz>
Date: Fri, 30 Sep 2011 13:15:14 -0700
From: Dave Hansen <dave@...ux.vnet.ibm.com>
To: Andrew Morton <akpm00@...il.com>
Cc: Vasiliy Kulikov <segoon@...nwall.com>, kernel-hardening@...ts.openwall.com,
Christoph Lameter
<cl@...ux-foundation.org>,
Pekka Enberg <penberg@...nel.org>, Matt Mackall
<mpm@...enic.com>,
linux-mm@...ck.org, Kees Cook <kees@...ntu.com>,
Valdis.Kletnieks@...edu,
Linus Torvalds <torvalds@...ux-foundation.org>,
David Rientjes <rientjes@...gle.com>, Alan Cox <alan@...ux.intel.com>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 2/2] mm: restrict access to /proc/meminfo
I stuck a printk in there. It's not exactly called 100x a second, but
there were 5 distinct users just for me to boot and ssh in:
[ 3.130408] meminfo read called by: 'udevd' 1
[ 3.326649] meminfo read called by: 'dhclient-script' 2
[ 4.624943] meminfo read called by: 'klogd' 3
[ 8.008019] meminfo read called by: 'dhclient-script' 4
[ 8.083091] meminfo read called by: 'ps' 5
[ 48.171038] meminfo read called by: 'bash' 6
Granted, those were likely privileged. But, that's a good list of
processes that I would rather not see break.
-- Dave
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
