| From | Willy Tarreau <> | Subject | [PATCH 3.10 259/319] net: clear sk_err_soft in sk_clone_lock() | Date | Sun, 5 Feb 2017 20:21:21 +0100 |
| |
From: Eric Dumazet <edumazet@google.com>
commit e551c32d57c88923f99f8f010e89ca7ed0735e83 upstream.
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> Signed-off-by: Willy Tarreau <w@1wt.eu> --- net/core/sock.c | 1 + 1 file changed, 1 insertion(+)
diff --git a/net/core/sock.c b/net/core/sock.c index 6473fef..e3cb454 100644 --- a/net/core/sock.c +++ b/net/core/sock.c @@ -1515,6 +1515,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; /* * Before updating sk_refcnt, we must commit prior changes to memory -- 2.8.0.rc2.1.gbe9624a
|