From: Eric Dumazet Date: Fri, 28 Oct 2016 20:40:24 +0000 (-0700) Subject: net: clear sk_err_soft in sk_clone_lock() X-Git-Tag: submit/tizen/20161219.112149~6^2~68 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=ac4c2cf6f57a399213478495dbf3315c01c797ab;p=sdk%2Femulator%2Femulator-kernel.git net: clear sk_err_soft in sk_clone_lock() [ Upstream commit e551c32d57c88923f99f8f010e89ca7ed0735e83 ] At accept() time, it is possible the parent has a non zero sk_err_soft, leftover from a prior error. Make sure we do not leave this value in the child, as it makes future getsockopt(SO_ERROR) calls quite unreliable. Signed-off-by: Eric Dumazet Acked-by: Soheil Hassas Yeganeh Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman --- diff --git a/net/core/sock.c b/net/core/sock.c index 0d91f7dca751..88f017854509 100644 --- a/net/core/sock.c +++ b/net/core/sock.c @@ -1562,6 +1562,7 @@ struct sock *sk_clone_lock(const struct sock *sk, const gfp_t priority) } newsk->sk_err = 0; + newsk->sk_err_soft = 0; newsk->sk_priority = 0; newsk->sk_incoming_cpu = raw_smp_processor_id(); atomic64_set(&newsk->sk_cookie, 0);