On 03/09/2012 12:38 PM, Ander Conselvan de Oliveira wrote:
On 03/09/2012 11:41 AM, Pekka Paalanen wrote:
On Fri, 9 Mar 2012 11:18:49 +0200
Ander Conselvan de Oliveira
wrote:
[...]
@@ -389,6 +393,18 @@ wl_message_size_extra(const struct wl_message
*message)
return extra;
}
+static void
+wl_con
Hi,
On 8 March 2012 18:20, Joakim Sindholt wrote:
> I think that wayland should be consistent across the board and act
> *only* as a display server and otherwise implement only the minimum set
> of features necessary for proper operation. That entails (what I think
> was the original intent) only
The buffer used by wl_connection_data to receive a cmsg is 128 bytes
long. This can hold at most 28 fds but when a cmsg is generated for
sending the fds, there is no check for this limitation. The man page
for recvmsg does not show any way of recovering from MSG_CTRUNC, that
happens when the buffer
On 03/09/2012 11:41 AM, Pekka Paalanen wrote:
On Fri, 9 Mar 2012 11:18:49 +0200
Ander Conselvan de Oliveira
wrote:
The buffer used by wl_connection_data to receive a cmsg is 128 bytes
long. This can hold at most 28 fds but when a cmsg is generated for
sending the fds, there is no check for thi
On Fri, 9 Mar 2012 11:18:49 +0200
Ander Conselvan de Oliveira
wrote:
> The buffer used by wl_connection_data to receive a cmsg is 128 bytes
> long. This can hold at most 28 fds but when a cmsg is generated for
> sending the fds, there is no check for this limitation. The man page
> for recvmsg d
The buffer used by wl_connection_data to receive a cmsg is 128 bytes
long. This can hold at most 28 fds but when a cmsg is generated for
sending the fds, there is no check for this limitation. The man page
for recvmsg does not show any way of recovering from MSG_CTRUNC, that
happens when the buffer