From f30b27a0ee9a41862b253fda07704d71b70b0e0e Mon Sep 17 00:00:00 2001
From: Julian Orth <ju.orth@gmail.com>
Date: Wed, 24 Apr 2024 10:44:59 +0200
Subject: [PATCH] security-context-v1: clarify close_fd behavior
Signed-off-by: Julian Orth <ju.orth@gmail.com>
---
staging/security-context/security-context-v1.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/staging/security-context/security-context-v1.xml b/staging/security-context/security-context-v1.xml
index 0b14078..a9ca9b8 100644
--- a/staging/security-context/security-context-v1.xml
+++ b/staging/security-context/security-context-v1.xml
@@ -68,7 +68,7 @@
sent by the client. In other words, the client must call bind(2) and
listen(2) before sending the FD.
- close_fd is a FD closed by the client when the compositor should stop
+ close_fd is a FD that will signal hangup when the compositor should stop
accepting new connections on listen_fd.
The compositor must continue to accept connections on listen_fd when
@@ -79,7 +79,7 @@
</description>
<arg name="id" type="new_id" interface="wp_security_context_v1"/>
<arg name="listen_fd" type="fd" summary="listening socket FD"/>
- <arg name="close_fd" type="fd" summary="FD closed when done"/>
+ <arg name="close_fd" type="fd" summary="FD signaling when done"/>
</request>
</interface>
--
GitLab