Le 20/02/2014 21:26, Thiago Macieira a écrit :
Em qui 20 fev 2014, às 19:56:08, Martin Peres escreveu:
Le 20/02/2014 18:42, Thiago Macieira a écrit :
Unless you meant that the WAYLAND_SOCKET variable can contain a file
descriptor number. Is that the case? In that case, how should the
privileged process clear the environment to allow child processes to be
launched?
Yes, it takes an FD as a parameter
(http://code.metager.de/source/xref/freedesktop/wayland/wayland/doc/man/wl_d
isplay_connect.xml#63).
The environment must be cleared automatically by the kernel because
weston must be very careful about opening resources with O_CLOEXEC.
I don't think you've understood my question.
Suppose Weston is careful already. It creates the socket, ensures it's no
O_CLOEXEC, sets WAYLAND_SOCKET and launches the privileged process.
Now, the privileged process wants to launch a sub-process. How will the sub-
process connect to the compositor? Remember: WAYLAND_SOCKET contains a file
descriptor number that isn't available to the child process.
Ah, I see. You are suggesting un-setting WAYLAND_SOCKET and using fcntl() to
set the socket's fd to CLOEXEC?
It is true that multiple process could end up with the same connection and
I didn't think about that. The problem is the same if an application
connects
to the compositor by itself and then forks. Not sure how the compositor
could detect that :s
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
