Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily

• Next message: Alan Cox: "Re: TOE brain dump"
• Previous message: jt.holmes@att.net: "Pcmcia Insertion causes Scheduler to hard Loop"
• In reply to: bert hubert: "Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily"
• Next in thread: Andrew Morton: "Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

Is that likely to happen on the kind of machines on which you will use
this option?

Also, if your purpose is to prevent userland from meddling with memory
you might want to block iopl was well.

Wichert.

-- 
Wichert Akkerman <wichert@wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.
-
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/

• Next message: Alan Cox: "Re: TOE brain dump"
• Previous message: jt.holmes@att.net: "Pcmcia Insertion causes Scheduler to hard Loop"
• In reply to: bert hubert: "Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily"
• Next in thread: Andrew Morton: "Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:22 EST