openbsd/src/regress/lib/libc/sys, branch libressl-v3.6.2 A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=libressl-v3.6.2 2022-09-11T20:51:44+00:00 Add regression tests for the sendmmsg and recvmmsg system calls. 2022-09-11T20:51:44+00:00 mbuhl 2022-09-11T20:51:44+00:00 urn:sha1:2306c513ba14d1a9d8b958302b55ac80974f070d *** empty log message *** 2022-05-28T18:39:39+00:00 mbuhl 2022-05-28T18:39:39+00:00 urn:sha1:40cea9c224dfe53bee31facb655f7ac9473c5148 Recent changes to truncate(2) swapped the ordering of some validations 2022-05-24T05:14:30+00:00 anton 2022-05-24T05:14:30+00:00 urn:sha1:1b3351c74f01f6fb9bd1b557012d9fd4d43ae9a8 causing EACCESS as opposed of ESDIR to be returned while trying to truncate a directory as a user lacking write permissions to the same directory. As this behavior is reasonable, change the truncate directory from /etc/ to /tmp which makes the test pass both as root and non-root. t_syscall was a test for the gcc 1.x off_t syscall padding, 2022-01-06T03:30:15+00:00 guenther 2022-01-06T03:30:15+00:00 urn:sha1:cb6132904d89fe3bdde57b1438faf9ad96a85173 which was an implementation detail and has been deleted, so delete the test remove a couple hundred sys/param.h includes in userland code, and 2021-12-13T16:56:48+00:00 deraadt 2021-12-13T16:56:48+00:00 urn:sha1:9021d14f9c0c87cbe273ab6f4fe8e4f48363f4f6 also whack some sys/cdefs.h early includes which is such a brutally bad pattern ok bluhm mbuhl For open/openat, if the flags parameter does not contain O_CREAT, the 2021-10-24T21:24:20+00:00 deraadt 2021-10-24T21:24:20+00:00 urn:sha1:2cbc009da6303d81a98bd284aae87c1761b472c7 3rd (variadic) mode_t parameter is irrelevant. Many developers in the past have passed mode_t (0, 044, 0644, or such), which might lead future people to copy this broken idiom, and perhaps even believe this parameter has some meaning or implication or application. Delete them all. This comes out of a conversation where tb@ noticed that a strange (but intentional) pledge behaviour is to always knock-out high-bits from mode_t on a number of system calls as a safety factor, and his bewilderment that this appeared to be happening against valid modes (at least visually), but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef. ok millert Remove recent changes used to unblock the signal undergoing testing, I solved it 2021-09-28T05:39:24+00:00 anton 2021-09-28T05:39:24+00:00 urn:sha1:76b51d8ea1cd63cb959c4f9b753386fa03bff58a by changing my regress environment instead. This reduces the delta to the NetBSD upstream. Make t_gettimeofday pass on sparc64. 2021-09-27T14:07:44+00:00 mbuhl 2021-09-27T14:07:44+00:00 urn:sha1:ec54265a51e657199218fe66ba025e97263136c4 OK bluhm@ At least t_fork and t_vfork tests need coredumps enabled to succeed. 2021-09-19T08:20:04+00:00 claudio 2021-09-19T08:20:04+00:00 urn:sha1:1377a15fedcd957ed14732db959a3c76892b80a6 Add ulimit -c unlimited before running the tests like it is done in other places in regress. OK bluhm@ Ensure that the kill signal undergoing testing is not ignored. 2021-09-09T17:36:34+00:00 anton 2021-09-09T17:36:34+00:00 urn:sha1:40f90f2357304c0308b36aac3cbdde2d09d7988c ok bluhm@