Arla 0.42-RC2

[Tomas Olsson]

Jeffrey Hutzelman <jhutz at cmu.edu> writes:
> Yup; you're going to have that problem with 2.6.16, because they went
> off and moved things into different sections.  Worse, if the kernel is
> compiled with CONFIG_DEBUG_RODATA, then on some platforms the system
> call table will actually be stored in read-only pages, and attempts to
> update it will result in a panic.
> 
How... oh well, as usual I guess. This is new for 2.6.16, right?

> We probably should do something about getting updated syscall table
> probing code back into Arla.
>
Or just throw the syscall code away. Do people really need it? Is it
possible to use the keyrings for reasonable pag storage nowadays?

/t