From: Michael Kerrisk Date: Mon, 28 Sep 2020 07:42:38 +0000 (+0200) Subject: seccomp.2: Rework SECCOMP_GET_NOTIF_SIZES somewhat X-Git-Tag: man-pages-5.12~84 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2bbe9bd9ae80fee9d34cfc9c7706d522f3be46ff;p=thirdparty%2Fman-pages.git seccomp.2: Rework SECCOMP_GET_NOTIF_SIZES somewhat The existing text says the structures (plural!) contain a 'struct seccomp_data'. But this is only true for the received notification structure (seccomp_notif). So, reword the sentence to be more general, noting simply that the structures may evolve over time. Add some comments to the structure definition. Signed-off-by: Michael Kerrisk --- diff --git a/man2/seccomp.2 b/man2/seccomp.2 index 5aa3d7c6f0..21b16fde36 100644 --- a/man2/seccomp.2 +++ b/man2/seccomp.2 @@ -267,9 +267,8 @@ must be a pointer to an unsigned 32-bit filter return action. .BR SECCOMP_GET_NOTIF_SIZES " (since Linux 5.0)" .\" commit 6a21cc50f0c7f87dae5259f6cfefe024412313f6 Get the sizes of the seccomp user-space notification structures. -Since the structures include a -.I "struct seccomp_data" -which may grow in size, this command can be used to determine how +Since these structures may evolve and grow over time, +this command can be used to determine how much memory to allocate for sending and receiving notifications. .IP The value of @@ -280,15 +279,13 @@ must be a pointer to a .IR "struct seccomp_notif_sizes" , which has the following form: .IP -.in +4n .EX struct seccomp_notif_sizes - __u16 seccomp_notif; - __u16 seccomp_notif_resp; - __u16 seccomp_data; + __u16 seccomp_notif; /* Size of notification structure */ + __u16 seccomp_notif_resp; /* Size of response structure */ + __u16 seccomp_data; /* Size of \(aqstruct seccomp_data\(aq */ }; .EE -.in .IP See .BR seccomp_unotify (2)