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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Dinsdag 28 Juni 2005 21:41, Christoph Lameter wrote:

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

Exactly. Mapping the readonly section readonly adds a nice way to
check that constant data is handled correctly by all of the code.
Otherwise, there might be some surprises if gcc performs
constant folding and we incorrectly rely on one copy to be writable.

A read-only text segment also raises the bar for authors of rootkits
or other evil hacks that patch the running kernel code.

Right now, s390 (and I believe arm, maybe others as well) is already
able to map in the readonly sections of the kernel from ROM, in order
to have more available RAM for other purposes.

	Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux