| From | Greg Kroah-Hartman <> | Subject | [PATCH 4.8 02/49] net: clear sk_err_soft in sk_clone_lock() | Date | Sat, 19 Nov 2016 10:22:54 +0100 |
| |
4.8-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <edumazet@google.com>
[ 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@google.com> Acked-by: Soheil Hassas Yeganeh <soheil@google.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> --- net/core/sock.c | 1 + 1 file changed, 1 insertion(+)
--- a/net/core/sock.c +++ b/net/core/sock.c @@ -1563,6 +1563,7 @@ struct sock *sk_clone_lock(const struct 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);
|