lkml.org 
[lkml]   [2015]   [Nov]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: use-after-free in sock_wake_async
    From
    Date
    On Wed, 2015-11-25 at 11:50 -0800, Eric Dumazet wrote:

    > > other->sk_data_ready(other);
    > > + unix_state_unlock(other);


    Also, problem with such construct is that we wakeup a thread that will
    block on the lock we hold.

    Beauty of sk_data_ready() is to call it once we hold no lock any more,
    to enable another cpu to immediately proceed.

    In this case, 'other' can not disappear, so it should be safe.




    \
     
     \ /
      Last update: 2015-11-25 21:41    [W:2.109 / U:0.156 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site