From: Eric Dumazet <edumazet@google.com>
Date: Fri, 28 Oct 2016 20:40:24 +0000 (-0700)
Subject: net: clear sk_err_soft in sk_clone_lock()
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=e551c32d57c88923f99f8f010e89ca7ed0735e83;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git

net: clear sk_err_soft in sk_clone_lock()

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 <edumazet@google.com>
Acked-by: Soheil Hassas Yeganeh <soheil@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
---

diff --git a/net/core/sock.c b/net/core/sock.c
index c73e28fc9c2a..df171acfe232 100644
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -1543,6 +1543,7 @@ struct sock *sk_clone_lock(const struct sock *sk, const gfp_t priority)
 		RCU_INIT_POINTER(newsk->sk_reuseport_cb, NULL);
 
 		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);