Do copy{in,out} early in the {g,s}etsockopt system call paths
commitde0003feb6bab70af69a82a906f4e463a00810f2
authorAggelos Economopoulos <aggelos@dragonflybsd.org>
Mon, 7 Jul 2008 14:35:12 +0000 (7 14:35 +0000)
committerAggelos Economopoulos <aggelos@dragonflybsd.org>
Mon, 7 Jul 2008 14:35:12 +0000 (7 14:35 +0000)
treeedd5ac30ff7af45af2486999c607153716745f9a
parent5a5f28f3059058e0fdf94a2df3f234a5fe1c260b
Do copy{in,out} early in the {g,s}etsockopt system call paths
so the rest of the kernel can assume it's dealing with a
kernel address in ->sopt_val. This means that soopt{,_m}copy{in,out}
are now seriously misnamed and should be replaced by soopt_{from,to}_*

Suggested-by: dillon@
sys/kern/uipc_msg.c
sys/kern/uipc_socket.c
sys/kern/uipc_syscalls.c