FreeBSD-stable-15-amd64-test - Build #897 - Still Unstable
Date: Sat, 27 Jun 2026 01:35:31 UTC
FreeBSD-stable-15-amd64-test - Build #897 (42d8b0bf7a5a074c7035585a06dd44aed1b2cbdd) - Still Unstable
Build information: https://ci.FreeBSD.org/job/FreeBSD-stable-15-amd64-test/897/
Full change log: https://ci.FreeBSD.org/job/FreeBSD-stable-15-amd64-test/897/changes
Full build log: https://ci.FreeBSD.org/job/FreeBSD-stable-15-amd64-test/897/console
Status explanation:
"Unstable" - some tests are suspected being broken by the following changes
"Still Unstable" - the failing test cases have not been fixed by these
following changes and this is a notification to note that
these changes have not been fully tested by the CI system
Change summaries:
(Those commits are likely but not certainly responsible)
a80e40ce9ee0a0641927730a193ff1f5641e71b6 by kib:
execve_block(): a mechanism for mutual exclusion with execve() on the
cbd58477285888b1b7ff21bdd0bc039f7ffad4ef by kib:
execve_block_pass(9): a helper to wait for the execblock to pass
be6e5131066753dc23f8e9f223acc023b7618b63 by kib:
proc: Allow to make proc_rwmem() operate on a consistent address space
3748c2e257046056b969a5d47231695798198f4d by kib:
kern_proc.c: ensure stability of the vmspace we read the strings from
20ed389b365030b868298d7ab4e8a01270c06c9f by kib:
kern_proc.c: ensure stability of the vmspace for sysctl kern.proc.vmmap
eb03358c407d6f3c073320bdc26a5e4ceb923ca1 by kib:
kern_proc.c: ensure stability of the vmspace for sysctl
5e633db3f8e126578c097c9649ba3be552664c6a by kib:
kern_proc.c: make kern.proc.osrel atomic
60d8df61846fc1f5f7e2a400d2b0237c9f1a6be8 by kib:
kern_proc.c: disallow execve around sysctl kern.proc.kstacks
24d8b3364405e5c32618c6930d4fdd8bc543a08f by kib:
kern_proc.c: disallow execve around sysctl kern.proc.rlimit
d172933cf69fb4dc58e07261653481a33cdf1da0 by kib:
kern_event: block the target process from execing for sysctl
035f66ff2924808f534df9065388aabf66e77266 by kib:
kern_resource.c: disallow execve around sysctl kern.proc.rlimitusage
d80a7fd6e6df65b4d85e6977557c3fbe8d9ff02e by kib:
kern_procctl(PROC_WX_MAPPINGS_PERMIT): ensure stability of the target
e9002239571fb1502505ff85061934ef0ebd2e1e by kib:
linux_prlimit(): block execve for the target
1744ce4b052d4aea94c1c3b87fefabd0952e6082 by kib:
pfs_readdir(): block the target process from execing
277f612073d0b086604448814867cadaacad4ca8 by kib:
pseudofs: ensure that the target process vmspace is stable for
78981848b85fdd826eb830dfdd6d92c14b0f8bb3 by kib:
procfs, linprocfs: ensure target process vmspace stability
e0492444761b638ff072222d39ba5d6088a63370 by kib:
sys_set*id(9): wait for the execblocks to pass
42d8b0bf7a5a074c7035585a06dd44aed1b2cbdd by kib:
kern_exec.c: explicitly include sys/limits.h for UINT_MAX
The failed test cases:
1 tests failed.
FAILED: sys.kern.aslr.aslr_setuid
Error Message:
/usr/src/tests/sys/kern/aslr.c:112: failed to find /sbin/ping text segment