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
Date: Sun, 3 Aug 2003 22:45:16 +0200 [thread overview]
Message-ID: <20030803204515.GA15271@outpost.ds9a.nl> (raw)
In-Reply-To: <20030803123218.7bb2c16f.akpm@osdl.org>
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
next prev parent reply other threads:[~2003-08-03 20:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 18:09 [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily bert hubert
2003-08-03 19:11 ` Willy Tarreau
2003-08-03 19:18 ` bert hubert
2003-08-03 20:26 ` Willy Tarreau
2003-08-03 21:37 ` Andries Brouwer
2003-08-03 19:32 ` Andrew Morton
2003-08-03 20:45 ` bert hubert [this message]
2003-08-03 20:52 ` Wichert Akkerman
2003-08-03 21:00 ` Andrew Morton
2003-08-03 21:33 ` David Lang
2003-08-03 21:47 ` bert hubert
2003-08-04 13:10 ` Alan Cox
2003-08-03 20:14 ` Matan Ziv-Av
2003-08-03 21:02 ` Alan Cox
2003-08-03 21:08 ` Erik Andersen
2003-08-04 12:30 ` eliezer
2003-08-04 9:37 ` devik
2003-08-04 13:46 ` bert hubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030803204515.GA15271@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=akpm@osdl.org \
--cc=devik@cdi.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox