sys_call_table in read-only section

[Richard B. Johnson]

Hello,
I noticed a patch this AM to put the syscall_table in with read-only
data. I didn't save the patch, but I put the sys_call_table in
.section .rodata. System.map shows that it's there. Tests show that 
the sys_call_table, even though in the so-called R/O section can
still be written. Is there a special R/O section that will truly
prevent kernel (driver) code from writing?

Cheers,
Dick Johnson
Penguin : Linux version 2.6.12 on an i686 machine (5537.79 BogoMips).
 Notice : All mail here is now cached for review by Dictator Bush.
                 98.36% of all statistics are fiction.
-
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/