XLibre/xserver
1
1
Fork 0
mirror of https://github.com/X11Libre/xserver.git synced 2026-03-24 08:04:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

dix: add some bit of documentation to privates subsystem

Browse Source 
Document some non-trivial aspects and add warnings what not to
touch in order to not breaking ABI.

Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
This commit is contained in:
Enrico Weigelt, metux IT consult
2025-10-21 13:48:17 +02:00
committed by Enrico Weigelt
parent 88bced1643
commit 182385af12
2 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
dix/privates.c
View File

@@ -337,6 +337,9 @@ dixRegisterPrivateKey(DevPrivateKey key, DevPrivateType type, unsigned size)
if (type == PRIVATE_XSELINUX) {
/* Resize if we can, or make sure nothing's allocated if we can't
*
* special magic for PRIVATE_XSELINUX type keys - those are registered
* at the same offset in several object types.
*/
for (DevPrivateType t = PRIVATE_XSELINUX; t < PRIVATE_LAST; t++)
if (xselinux_private[t]) {

12
include/privates.h
View File

@@ -24,8 +24,18 @@ CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
typedef struct _Private PrivateRec, *PrivatePtr;
/* WARNING: the values, as well as the total number are part of public ABI.
Adding a new one will lead to increased size as well as different field
offsets within ScreenRec.
*/
typedef enum {
/* XSELinux uses the same private keys for numerous objects */
/* XSELinux uses the same private keys for numerous objects
This black magic - keys of this type have very special handling:
their corresponding space is allocated at the top of the private
areas, in *several* object types (see xselinux_private[] array),
and xselinux uses the same keys for all object types
*/
PRIVATE_XSELINUX,
/* Otherwise, you get a private in just the requested structure