Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 3 Mar 2001 14:14:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 3 Mar 2001 14:13:57 -0500 Received: from leibniz.math.psu.edu ([146.186.130.2]:5071 "EHLO math.psu.edu") by vger.kernel.org with ESMTP id ; Sat, 3 Mar 2001 14:13:44 -0500 Date: Sat, 3 Mar 2001 14:13:41 -0500 (EST) From: Alexander Viro To: Denis Perchine cc: linux-kernel@vger.kernel.org Subject: Re: Q: How to get physical memory size from user space without proc fs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 3 Mar 2001, Denis Perchine wrote: > Hello, > > actually the question is in subj. > Problem is that there is a program which needs to know physical memory > size. This information is used to justify memory consumption as after some > swapping performance is drops dramatically, and it is better to finish. > > I know that this is not the best idea, but it is assumed that this program > is the only one running on the machine. > > I do not want to use proc as some people can just do not mount it. > > Any comments, suggestions? In initscripts create a directory with mode=700. Create a subdirectory there. Mount procfs on it. Get the information. umount. rmdir. rmdir. Put that information into /etc. Let your program use that as config file. If attacker is able to traverse root-owned directory with rwx------ when initscripts are run he won't gain anything new from accessing procfs, since he already can do whatever he bloody wants. Besides, that way it's easy to port to non-Linux boxen - all system dependencies are in the way to have /etc/memsize set by the time when your program is run. Which can be done by echo/ed/vi/whatever. Cheers, Al - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/