On Tue, Mar 26, 2013 at 05:25:50PM +0100, Juan Quintela wrote:
Stefan Hajnoczi stefa...@redhat.com wrote:
There are several code paths in net_init_socket() depending on how the
socket is created: file descriptor passing, UDP multicast, TCP, or UDP.
Some of these support both listen and
On Tue, Mar 26, 2013 at 10:33:45AM -0600, Eric Blake wrote:
On 03/26/2013 10:07 AM, Stefan Hajnoczi wrote:
There are several code paths in net_init_socket() depending on how the
socket is created: file descriptor passing, UDP multicast, TCP, or UDP.
Some of these support both listen and
There are several code paths in net_init_socket() depending on how the
socket is created: file descriptor passing, UDP multicast, TCP, or UDP.
Some of these support both listen and connect.
Not all code paths set the socket to non-blocking. This patch addresses
the file descriptor passing and
On 03/26/2013 10:07 AM, Stefan Hajnoczi wrote:
There are several code paths in net_init_socket() depending on how the
socket is created: file descriptor passing, UDP multicast, TCP, or UDP.
Some of these support both listen and connect.
Not all code paths set the socket to non-blocking.
Stefan Hajnoczi stefa...@redhat.com wrote:
There are several code paths in net_init_socket() depending on how the
socket is created: file descriptor passing, UDP multicast, TCP, or UDP.
Some of these support both listen and connect.
Not all code paths set the socket to non-blocking. This