| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
a race in which one thread is currently initializing the mutex which is
not an atomic operation whereas another thread tries to use it too
early.
With and ok schwarze@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
no_sanitize_address attribute. ASAN doesn't seem to be able
to understand these lowlevel gymnastics with sigaltstack()
and segfaults in __intercept_memem().
This allows LibreSSL and other portable projects that use this
test run tests with ASAN enabled.
Issue reported and workaround suggested by Ilya Shipitsin
Paraphrasing millert: it's a little ugly but it's only a regress.
|
|
|
|
| |
int foo() to int foo(void)
|
|
|
|
|
|
|
|
| |
... including those inlined into print_dname(). This also fixes
-Wunused-but-set-variable warnings warnings in smtpd and smtpctl.
The code was imported with asr and then copied around.
ok deraadt@ guenther@
|
| |
|
|
|
|
|
| |
which was an implementation detail and has been deleted, so
delete the test
|
|
|
|
|
|
| |
also whack some sys/cdefs.h early includes which is such a brutally
bad pattern
ok bluhm mbuhl
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
by changing my regress environment instead. This reduces the delta to the NetBSD
upstream.
|
|
|
|
|
|
| |
This makes the test pass on sparc64 where the compiler may otherwise
store the variable in the strlcpy/strlcat function's delay slot.
OK kettenis@
|
| |
|
|
|
|
| |
OK bluhm@
|
|
|
|
|
|
| |
Add ulimit -c unlimited before running the tests like it is done in
other places in regress.
OK bluhm@
|
|
|
|
| |
ok bluhm@
|
| |
|
|
|
|
|
| |
exec/exit with vfork.
OK bluhm@
|
|
|
|
| |
OK bluhm@
|
|
|
|
| |
spotted by anton
|
|
|
|
|
|
|
| |
these options should be set globally (sysctl) when running regress as opposed to having
individual tests set it, barring a few specific exceptions.
ok bluhm@
|
| |
|
|
|
|
| |
prompted by the bug krw@ fixed yesterday in uuid_from_string()
|
|
|
|
| |
ok bluhm@
|
| |
|
|
|
|
| |
end statements with ';' because ',' isn't enough
|
| |
|
| |
|
|
|
|
|
|
|
| |
did not terminate anymore on some machines. The test counts 100
send errors before it finishes. NetBSD has added sched_yield() in
the receiver loop to trigger the errors on the sender side. Although
not perfect, it works for me. Get current t_sendrecv.c from NetBSD.
|
|
|
|
|
|
|
| |
and rounding control bits are not restored by longjmp(3). So expect
the some failures on that platform.
ok bluhm@
|
|
|
|
|
| |
similar that have no isssues. Reported by Michael Paoli. Failing
cases commented out for now.
|
|
|
|
| |
ok bluhm@, inoguchi@, tb@, deraadt@
|
| |
|
|
|
|
| |
From miod@, OK tb@
|
|
|
|
|
| |
an OOR2 operator. Also includes a regress test for the issue.
From FreeBSD via miod@
|
| |
|
| |
|
|
|
|
| |
pass when run as non root.
|
| |
|
|
|
|
|
|
|
| |
to document differences to NetBSD behaviour, this helps to track
upstream. Mark currently failing test as expected failures. So
test programs get compiled and executed, but it shows that further
investigation is necceassry.
|
|
|
|
|
|
|
|
| |
syscall. So whenever we pass a bad address we get a SIGSEGV instead of
EFAULT. POSIX explicitly allows this behaviour. So adjust the test
to deal with this case.
ok deraadt@, millert@, guenther@
|
|
|
|
|
|
| |
(typically) doesn't implement support for these.
ok patrick@, drahn@
|
|
|
|
| |
optional and isn't implemented on most hardware.
|
| |
|
|
|
|
| |
OK deraadt@ martijn@
|
|
|
|
|
|
| |
Makes the test work on architectures where char is unsigned.
ok deraadt@, millert@
|
|
|
|
| |
and for their modifiers, written from scratch.
|
|
|
|
| |
and for their modifiers, written from scratch.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This diff exposes parts of clock_gettime(2) and gettimeofday(2) to
userland via libc eliberating processes from the need for a context
switch everytime they want to count the passage of time.
If a timecounter clock can be exposed to userland than it needs to set
its tc_user member to a non-zero value. Tested with one or multiple
counters per architecture.
The timing data is shared through a pointer found in the new ELF
auxiliary vector AUX_openbsd_timekeep containing timehands information
that is frequently updated by the kernel.
Timing differences between the last kernel update and the current time
are adjusted in userland by the tc_get_timecount() function inside the
MD usertc.c file.
This permits a much more responsive environment, quite visible in
browsers, office programs and gaming (apparently one is are able to fly
in Minecraft now).
Tested by robert@, sthen@, naddy@, kmos@, phessler@, and many others!
OK from at least kettenis@, cheloha@, naddy@, sthen@
|
|
|
|
|
|
| |
aarch64/powerpc/powerpc64, making use of the count leading
zeros instruction. Also add a brief regression test.
ok deraadt@ kettenis@
|
|
|
|
|
|
| |
Issue reported with initial patch by enh@google.com.
ok deraadt@
|