[PATCH 3.16 331/370] net: clear sk_err_soft in sk_clone_lock()
From: Ben Hutchings
Date: Fri Mar 10 2017 - 08:29:53 EST
3.16.42-rc1 review patch. If anyone has any objections, please let me know.
From: Eric Dumazet <edumazet@xxxxxxxxxx>
[ 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 <edumazet@xxxxxxxxxx>
Acked-by: Soheil Hassas Yeganeh <soheil@xxxxxxxxxx>
Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx>
Signed-off-by: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
net/core/sock.c | 1 +
1 file changed, 1 insertion(+)
@@ -1560,6 +1560,7 @@ struct sock *sk_clone_lock(const struct
newsk->sk_err = 0;
+ newsk->sk_err_soft = 0;
newsk->sk_priority = 0;
* Before updating sk_refcnt, we must commit prior changes to memory