From: Rik van Riel (riel_at_surriel.com)
Date: Sun 31 Aug 2003 - 15:57:42 BST
I just started reading the vserver patch again and am now
officially scared to hell:
.long SYMBOL_NAME(sys_ni_syscall) /* sys_free_hugepages */
.long SYMBOL_NAME(sys_ni_syscall) /* sys_exit_group */
+ .long SYMBOL_NAME(sys_new_s_context)
+ .long SYMBOL_NAME(sys_set_ipv4root)
.long SYMBOL_NAME(sys_ni_syscall) /* sys_lookup_dcookie */
.long SYMBOL_NAME(sys_ni_syscall) /* sys_epoll_create */
This patch fragment to entry.S adds two syscalls into the
middle of the table, shifting the syscalls below it to
Does vserver have reserved syscall numbers already ?
If so, are there any plans to get them ?
How about a sys_vserver multiplexer so we can easily add
things like setting a new ipv6 root to the interface,
without needing yet another syscall ?
-- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan