Alan Somers 0125d6a23b libcasper: document that most libcasper functions are not thread-safe ... And neither are most libcasper services' functions, because internally they all use cap_xfer_nvlist. cap_xfer_nvlist sends and then receives data over a unix domain socket and associated with the cap_channel_t argument. So absent synchronization, two threads may not use the same cap_channel_t argument or they risk receiving the other's reply. Sponsored by: Axcient Reviewed by: oshogbo Differential Revision: https://reviews.freebsd.org/D42928 (cherry picked from commit cf037972ea)		2024-01-19 18:51:58 -07:00
..
tests	Remove $FreeBSD$: one-line sh pattern	2023-08-16 11:55:03 -06:00
cap_pwd.3	libcasper: document that most libcasper functions are not thread-safe	2024-01-19 18:51:58 -07:00
cap_pwd.c	Remove $FreeBSD$: one-line .c pattern	2023-08-16 11:54:42 -06:00
cap_pwd.h	Remove $FreeBSD$: two-line .h pattern	2023-08-16 11:54:16 -06:00
Makefile	libcasper: Neuter false positive -Wuse-after-free warnings from GCC 13	2024-01-03 09:43:47 -08:00
Makefile.depend	Remove $FreeBSD$: one-line sh pattern	2023-08-16 11:55:03 -06:00