Re: [PATCH] Read only syscall tables for x86_64 and i386

[Christoph Lameter]

On Tue, 28 Jun 2005, Andi Kleen wrote:

> It's unfortunately useless because all the kernel is mapped in the
> same 2 or 4MB page has to be writable because it overlaps with real
> direct mapped memory.

The question is: Are syscall tables are supposed to be 
writable? If no then this patch should go in. If yes then forget about it.
On IA64 they are readonly and so I thought they should also be readonly
on i386 and x86_64.

The ability to protect a readonly section may be another issue.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/