lkml.org 
[lkml]   [2017]   [Mar]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Date
    Subject[PATCH 3.2 168/199] net: clear sk_err_soft in sk_clone_lock()
    3.2.87-rc1 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: Ben Hutchings <ben@decadent.org.uk>
    ---
    net/core/sock.c | 1 +
    1 file changed, 1 insertion(+)

    --- a/net/core/sock.c
    +++ b/net/core/sock.c
    @@ -1259,6 +1259,7 @@ struct sock *sk_clone(const struct sock
    }

    newsk->sk_err = 0;
    + newsk->sk_err_soft = 0;
    newsk->sk_priority = 0;
    /*
    * Before updating sk_refcnt, we must commit prior changes to memory
    \
     
     \ /
      Last update: 2017-03-10 13:03    [W:4.052 / U:0.372 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site