[lkml]   [2003]   [Aug]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily
On Sun, Aug 03, 2003 at 12:32:18PM -0700, Andrew Morton wrote:
> bert hubert <> 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?


-- Open source, database driven DNS Software Linux Advanced Routing & Traffic Control HOWTO
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:47    [W:0.086 / U:11.916 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site