Searched hist:"5 b1df30051c3340cc5945def344ffaaee19d7361" (Results 1 – 2 of 2) sorted by relevance
/freebsd/sys/compat/freebsd32/ |
H A D | syscalls.conf | diff 5b1df30051c3340cc5945def344ffaaee19d7361 Wed Nov 14 01:46:02 CET 2018 Brooks Davis <brooks@FreeBSD.org> Use the main capabilities.conf for freebsd32.
Allow the location of capabilities.conf to be configured.
Also allow a per-abi syscall prefix to be configured with the abi_func_prefix syscalls.conf variable and check syscalls against entries in capabilities.conf with and without the prefix amended.
Take advantage of these two features to allow use shared capabilities.conf between the default syscall vector and the freebsd32 compatability layer. We've been inconsistent about keeping the two in sync as evidenced by the bugs fixed in r340294. This eliminates that problem going forward.
Reviewed by: kib Obtained from: CheriBSD Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D17932
|
H A D | Makefile | diff 5b1df30051c3340cc5945def344ffaaee19d7361 Wed Nov 14 01:46:02 CET 2018 Brooks Davis <brooks@FreeBSD.org> Use the main capabilities.conf for freebsd32.
Allow the location of capabilities.conf to be configured.
Also allow a per-abi syscall prefix to be configured with the abi_func_prefix syscalls.conf variable and check syscalls against entries in capabilities.conf with and without the prefix amended.
Take advantage of these two features to allow use shared capabilities.conf between the default syscall vector and the freebsd32 compatability layer. We've been inconsistent about keeping the two in sync as evidenced by the bugs fixed in r340294. This eliminates that problem going forward.
Reviewed by: kib Obtained from: CheriBSD Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D17932
|