Date: Sun, 3 Aug 2003 22:45:16 +0200
From: bert hubert <ahu@ds9a.nl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, devik@cdi.cz
Subject: Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily
Message-ID: <20030803204515.GA15271@outpost.ds9a.nl>
Mail-Followup-To: bert hubert <ahu@ds9a.nl>,
	Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org,
	devik@cdi.cz
References: <20030803180950.GA11575@outpost.ds9a.nl> <20030803123218.7bb2c16f.akpm@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030803123218.7bb2c16f.akpm@osdl.org>
User-Agent: Mutt/1.3.28i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1064
Lines: 27

On Sun, Aug 03, 2003 at 12:32:18PM -0700, Andrew Morton wrote:
> bert hubert <ahu@ds9a.nl> wrote:
> >
> >  +#if defined(CONFIG_MEMORY_ACCESS)
> >   	{1, "mem",     S_IRUSR | S_IWUSR | S_IRGRP, &mem_fops},
> >   	{2, "kmem",    S_IRUSR | S_IWUSR | S_IRGRP, &kmem_fops},
> >  +#endif	
> 
> Well if you're going to do this, wouldn't it be better to force a segv and
> drop some messages in syslog?

problem with sigsegv is that it does not allow legitimate programs to choose
an alternate approach - the log entry would be nice though.

as one of the 'tastemasters', what are your thoughts on doing this
dynamically? The sigsegv option might be a dynamic option?

Thanks.

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
-
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/