diff options
| author | Stefan Hajnoczi | 2015-11-04 13:58:42 +0100 |
|---|---|---|
| committer | David S. Miller | 2015-11-05 04:03:10 +0100 |
| commit | 7362945aea72fccc9df4f4e7643c971e0a8c33dc (patch) | |
| tree | 778462f9edd824275b8fe7469d9a860800e87ac1 /block | |
| parent | tun_dst: Fix potential NULL dereference (diff) | |
| download | kernel-qcow2-linux-7362945aea72fccc9df4f4e7643c971e0a8c33dc.tar.gz kernel-qcow2-linux-7362945aea72fccc9df4f4e7643c971e0a8c33dc.tar.xz kernel-qcow2-linux-7362945aea72fccc9df4f4e7643c971e0a8c33dc.zip | |
VSOCK: call sk->sk_data_ready() on accept()
When a listen socket enqueues a connection for userspace to accept(),
the sk->sk_data_ready() callback should be invoked. In-kernel socket
users rely on this callback to detect when incoming connections are
available.
Currently the sk->sk_state_change() callback is invoked by
vmci_transport.c. This happens to work for userspace applications since
sk->sk_state_change = sock_def_wakeup() and sk->sk_data_ready =
sock_def_readable() both wake up the accept() waiter. In-kernel socket
users, on the other hand, fail to detect incoming connections.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions