linux-kernel - Re: [PATCH] VSOCK: call sk->sk_data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20151104.220332.1882923396348027768.davem@davemloft.net>
Date:	Wed, 04 Nov 2015 22:03:32 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	stefanha@...hat.com
Cc:	netdev@...r.kernel.org, thellstrom@...are.com, asarwade@...are.com,
	jhansen@...are.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] VSOCK: call sk->sk_data_ready() on accept()

From: Stefan Hajnoczi <stefanha@...hat.com>
Date: Wed,  4 Nov 2015 12:58:42 +0000

> 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@...hat.com>

Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/