Displaying 3 results from an estimated 3 matches for "fd_device".
Did you mean:
id_device
2017 Mar 08
1
Suspicious code in net_socket.c
...ccurance of ai_next ==
NULL.
But it works. Linux, Windows, coordinator with white IP, other nodes behind
NAT's (1 or two NAT's, only direct connections allowed).
There are some problems with MinGW make, at least - mingw-64 from Fedora 25.
1. No definition for ETH_HLEN and ETHER_TYPE_LEN (fd_device.c)
2. no "kill" function in mingw (tincctl.c)
3. curses and readline from Fedora's mingw not directly compatible with tinc
configuration scripts - i want ti check it in some days and put patch to
.spec
For now I use dirty hacks to work around problems.
For now:
Packages for Fedora...
2015 Sep 16
0
[ANNOUNCE] libdrm 2.4.65
...d -lm to LDADD for dristat
Rafał Sapała (1):
intel: Serialize drmPrimeFDToHandle with struct_mutex
Rob Clark (4):
freedreno: don't take ownership of the dmabuf fd on import
drm: make individual drm_server_info fxns optional
freedreno: add API to get drm fd from fd_device
Bump version for release
Thierry Reding (1):
omap: Initialize DMA BUF file descriptor to -1
Tvrtko Ursulin (1):
libdrm: Add framebuffer modifiers uapi
Varad Gautam (5):
freedreno: fix a bo cache segfault with imported bo's
freedreno: fill bo->fd w...
2017 Mar 06
2
Suspicious code in net_socket.c
Good afternoon!
Module - net_socket.c
Function - get_known_addresses
---------------------------------------------------
struct addrinfo *nai = xzalloc(sizeof *nai);
if(ai)
ai->ai_next = nai;
ai = nai;
--------------------------------------------------
For my opinion, possible causes:
1. Lost trails (ai_next)
2. ai_next not initialized
3. Possible segfault during