On Tue, 6 Mar 2007, Johannes Berg wrote:
> The function reads as follows:
>
> int compat_sock_common_getsockopt(struct socket *sock, int level, int optname,
> char __user *optval, int __user *optlen)
> {
> struct sock *sk = sock->sk;
>
> if (sk->sk_prot->compat_setsockopt != NULL)
> ^^^
>
> return sk->sk_prot->compat_getsockopt(sk, level, optname,
> ^^^
> optval, optlen);
> return sk->sk_prot->getsockopt(sk, level, optname, optval, optlen);
> }
> EXPORT_SYMBOL(compat_sock_common_getsockopt);
>
> Is that intentional to make protocol writers assign both if they want
> compat_setsockopt? :P
It's a bug.
--
James Morris
<[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
