Re: [PATCH net] net: clear sk_err_soft in sk_clone_lock()

2016-10-31 Thread David Miller
From: Eric Dumazet Date: Fri, 28 Oct 2016 13:40:24 -0700 > From: Eric Dumazet > > 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

Re: [PATCH net] net: clear sk_err_soft in sk_clone_lock()

2016-10-28 Thread Soheil Hassas Yeganeh
On Fri, Oct 28, 2016 at 4:40 PM, Eric Dumazet wrote: > From: Eric Dumazet > > 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 unrelia

[PATCH net] net: clear sk_err_soft in sk_clone_lock()

2016-10-28 Thread Eric Dumazet
From: Eric Dumazet 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 --- net/core/sock.c |1 +