e881934927
We can't just unconditionally read the optional arguments (and also read it as a void* despite actually being an int). While this happens to work on most architectures because the first few variadic arguments are passed in registers, this is non-portable and causes a crash on architectures that set bounds on variadic function arguments (for example CHERI-enabled architectures). It could also cause problems on big-endian architectures that pass variadic arguments on the stack rather than in registers. For CHERI-MIPS, reading sizeof(void*) causes a read of 16 bytes from the bounded varargs capability. This always crashes since even calls with the optional argument only have 4 bytes available. Signed-off-by: Alex Richardson <Alexander.Richardson@cl.cam.ac.uk> Reviewed-by: Simon Ser <contact@emersion.fr> |
||
---|---|---|
.gitlab/issue_templates | ||
cursor | ||
doc | ||
egl | ||
protocol | ||
src | ||
tests | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
CONTRIBUTING.md | ||
COPYING | ||
meson_options.txt | ||
meson.build | ||
publish-doc | ||
README | ||
releasing.txt | ||
wayland-scanner.m4 | ||
wayland-scanner.mk |
What is Wayland? Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers. The wayland protocol is essentially only about input handling and buffer management. The compositor receives input events and forwards them to the relevant client. The clients creates buffers and renders into them and notifies the compositor when it needs to redraw. The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor. However, the protocol does not handle rendering, which is one of the features that makes wayland so simple. All clients are expected to handle rendering themselves, typically through cairo or OpenGL. The weston compositor is a reference implementation of a wayland compositor and the weston repository also includes a few example clients. Building the wayland libraries is fairly simple, aside from libffi, they don't have many dependencies: $ git clone https://gitlab.freedesktop.org/wayland/wayland $ cd wayland $ meson build/ --prefix=PREFIX $ ninja -C build/ install where PREFIX is where you want to install the libraries. See https://wayland.freedesktop.org for more complete build instructions for wayland, weston, xwayland and various toolkits.