Messages in this thread | | | Subject | Re: use-after-free in sock_wake_async | From | Eric Dumazet <> | Date | Wed, 25 Nov 2015 12:23:37 -0800 |
| |
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.
| |