Changes in Makefile

Changes in Makefile http://nxr.netbsd.org/rss/src/tests/lib/libc/sys/Makefile en Copyright 2005 Java Commit GSoC 2025 aio project by Ethan Miller: https://blog.netbsd.org/tnf/entry/gsoc2025_asynchronous_i_o_framework /src/tests/lib/libc/sys/Makefile - 1.80 Fri Oct 10 15:53:55 UTC 2025 christos tests/lib/libc/sys/Makefile: Fix truncate_test.root_owned output. Announce the creation of this file with ${_MKTARGET_CREATE}, not with cryptic dd(1) output. And just use touch(1) instead of dd from /dev/null, simpler and clearer what's going on. No functional change intended, other than to the cosmetics of build output. /src/tests/lib/libc/sys/Makefile - 1.79 Fri May 09 13:18:32 UTC 2025 riastradh t_poll: Expand tests of polling when other endpoint is closed. This covers fifos, pipes, and sockets; reads and writes; and polling when the endpoint is already closed as well as sleeping until the endpoint is closed after a delay. Unfortunately, there is disagreement right now between: (a) POSIX, (b) our poll(2) man page, and (c) our implementation, for many of these cases. And we recently changed the behaviour of poll(2) on fifos between 9 and 10 (PR kern/56429: poll(2) should yield POLLHUP when last writer to a fifo close()'s it) but didn't get it quite right. So I've annotated these test cases with xfails for all the cases I think we're currently doing wrong -- under a justification from some combination of POSIX, our own documentation, and/or a reasonable interpretation of what the semantics _should_ be based on how read(2) and write(2) will behave. These are mostly edge cases: 1. [pollclosed_pipe_*_write*] When the read side of a pipe is closed, poll(2) on the write side currently returns POLLHUP|POLLOUT, which POSIX forbids because it requires POLLHUP to be mutually exclusive with POLLOUT. And our man page concurs with POSIX on this rule, and has for a long time (going as far back as NetBSD 1.3 or earlier, judging by https://man.NetBSD.org/NetBSD-1.3/poll.2). => Fixing this won't change whether anything wakes up earlier or later -- it will only change which bits are set when the wakeups happen. 2. [pollclosed_fifo*_immediate_readsome] When the write side of a fifo was previously open with the read side, and has since been closed before calling poll(2), poll(2) on the read side returns 0 instead of POLLHUP|POLLIN as it is expected to, even though read(2) will return EOF without blocking. => Fixing this may lead to more wakeups than before, but only in cases where read(2) would actually return immediately anyway. 3. [pollclosed_fifo*_delayed_*_read] When the write side of a fifo is closed, poll(2) on the read side returns POLLHUP|POLLIN, as it is expected to. But this state currently isn't persistent, even though the behaviour of read(2) in returning EOF without blocking is persistent. => Fixing this may lead to more wakeups than before, but only in cases where read(2) would actually return immediately anyway. That said, it turns out that we are correct, according to POSIX, in not setting POLLHUP on a socket whose peer has been closed: POLLHUP is only for devices, pipes, and FIFOs. So one of the issues I reported in PR 59056 turns out to be bogus. (Also POLLHUP is only for the reader side anyway, not for the writer side.) https://pubs.opengroup.org/onlinepubs/9799919799/functions/poll.html PR kern/59056: poll POLLHUP bugs /src/tests/lib/libc/sys/Makefile - 1.78 Sun Feb 09 17:10:37 UTC 2025 riastradh PR/58896: Martin Husemann: Demonstrate that a PT_STOPed process could not be PT_KILLed. /src/tests/lib/libc/sys/Makefile - 1.77 Tue Dec 17 17:52:23 UTC 2024 christos branches: 1.76.2; t_setrlimit: Narrow the scope of stack-protector warning suppression. /src/tests/lib/libc/sys/Makefile - 1.76 Thu Dec 07 16:54:44 UTC 2023 riastradh t_setrlimit uses alloca now /src/tests/lib/libc/sys/Makefile - 1.75 Fri Nov 24 17:19:55 UTC 2023 christos introduce new GCC 12 warning disables and use them in a few places this introduces 4 new warning disable flags: CC_WNO_MISSING_TEMPLATE_KEYWORD CC_WNO_REGISTER CC_WNO_STRINGOP_OVERREAD CC_WNO_ARRAY_BOUNDS and documents them in README.warnings. of these, the string op and array bounds are both problematic (real bugs) and also spurious (not real bugs), and the other 2 are mostly temporary for older 3rd party code. add some new uses of CC_WNO_STRINGOP_OVERFLOW. fix m68k build for gallium and GCC 12. /src/tests/lib/libc/sys/Makefile - 1.74 Tue Aug 08 06:27:32 UTC 2023 mrg bsd.own.mk: rename to CC_WNO_ADDRESS_OF_PACKED_MEMBER Provide a single variable CC_WNO_ADDRESS_OF_PACKED_MEMBER with options for both clang and gcc, to replace CLANG_NO_ADDR_OF_PACKED_MEMBER CC_NO_ADDR_OF_PACKED_MEMBER GCC_NO_ADDR_OF_PACKED_MEMBER Using the convention CC_compilerflag, where compilerflag is based on the full compiler flag name. /src/tests/lib/libc/sys/Makefile - 1.73 Sat Jun 03 08:52:59 UTC 2023 lukem branches: 1.72.2; Provide _GNU_SOURCE for t_clone now that is required to make clone() visible. /src/tests/lib/libc/sys/Makefile - 1.72 Mon Aug 01 15:48:39 UTC 2022 kre Add a regression test for PR kern/52239, "Changing protections of already mmap'ed region can fail", based on the test program in the PR. /src/tests/lib/libc/sys/Makefile - 1.71 Wed Apr 06 10:02:55 UTC 2022 gson Test lib/libc/sys/t_timerfd often fails when run on QEMU because QEMU misses clock interrupts. Always check values against [ lower, upper ] bounds and use "4 * upper" when run under QEMU. Now becomes part of PR kern/43997 "Kernel timer discrepancies". /src/tests/lib/libc/sys/Makefile - 1.70 Mon Nov 01 14:33:41 UTC 2021 hannken Add native implementations of eventfd(2) and timerfd(2), compatible with the Linux interfaces of the same name. /src/tests/lib/libc/sys/Makefile - 1.69 Sun Sep 19 15:51:28 UTC 2021 thorpej branches: 1.68.2; add support for new GCC 9 warnings that may be too much to fix right now. new address-of-packed-member and format-overflow warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd GCC_NO_FORMAT_OVERFLOW variables to remove these warnings. apply to a bunch of the tree. mostly, these are real bugs that should be fixed, but in many cases, only by removing the 'packed' attribute from some structure that doesn't really need it. (i looked at many different ones, and while perhaps 60-80% were already properly aligned, it wasn't clear to me that the uses were always coming from sane data vs network alignment, so it doesn't seem safe to remove packed without careful research for each affect struct.) clang already warned (and was not erroring) for many of these cases, but gcc picked up dozens more. /src/tests/lib/libc/sys/Makefile - 1.68 Sun Sep 06 07:20:31 UTC 2020 mrg New system call getrandom() compatible with Linux and others. Three ways to call: getrandom(p, n, 0) Blocks at boot until full entropy. Returns up to n bytes at p; guarantees up to 256 bytes even if interrupted after blocking. getrandom(0,0,0) serves as an entropy barrier: return only after system has full entropy. getrandom(p, n, GRND_INSECURE) Never blocks. Guarantees up to 256 bytes even if interrupted. Equivalent to /dev/urandom. Safe only after successful getrandom(...,0), getrandom(...,GRND_RANDOM), or read from /dev/random. getrandom(p, n, GRND_RANDOM) May block at any time. Returns up to n bytes at p, but no guarantees about how many -- may return as short as 1 byte. Equivalent to /dev/random. Legacy. Provided only for source compatibility with Linux. Can also use flags|GRND_NONBLOCK to fail with EWOULDBLOCK/EAGAIN without producing any output instead of blocking. - The combination GRND_INSECURE|GRND_NONBLOCK is the same as GRND_INSECURE, since GRND_INSECURE never blocks anyway. - The combinations GRND_INSECURE|GRND_RANDOM and GRND_INSECURE|GRND_RANDOM|GRND_NONBLOCK are nonsensical and fail with EINVAL. As proposed on tech-userlevel, tech-crypto, tech-security, and tech-kern, and subsequently adopted by core (minus the getentropy part of the proposal, because other operating systems and participants in the discussion couldn't come to an agreement about getentropy and blocking semantics): https://mail-index.netbsd.org/tech-userlevel/2020/05/02/msg012333.html /src/tests/lib/libc/sys/Makefile - 1.67 Fri Aug 14 00:53:16 UTC 2020 riastradh Add ppoll() a compatibility wrapper around pollts(2) Submitted by Apurva Nandan. /src/tests/lib/libc/sys/Makefile - 1.66 Fri Jul 17 15:34:16 UTC 2020 kamil Fix build for vax; Compile t_ptrace_sigchld.c with -D__TEST_FENV. /src/tests/lib/libc/sys/Makefile - 1.65 Wed Jun 17 22:07:21 UTC 2020 rin Add a test for sigaltstack(2) and SA_ONSTACK /src/tests/lib/libc/sys/Makefile - 1.64 Thu Apr 30 11:03:29 UTC 2020 ryo Add a NetBSD native futex implementation, mostly written by riastradh@. Map the COMPAT_LINUX futex calls to the native ones. /src/tests/lib/libc/sys/Makefile - 1.63 Sun Apr 26 18:53:33 UTC 2020 thorpej PR/55177: Carlo Arenas: mremap(MAP_REMAPDUP) fails after fork() /src/tests/lib/libc/sys/Makefile - 1.62 Sat Apr 18 17:44:53 UTC 2020 christos Add new ptrace(2) test file t_ptrace_sigchld - for SIGCHLD handler + ptrace(2). Right now a single test is enabled (raise(SIGKILL)) and marked as failed as it never finishes as the child is never collected before exiting the parent uninterested about its child (SA_NOCLDWAIT). /src/tests/lib/libc/sys/Makefile - 1.61 Fri Mar 06 18:32:35 UTC 2020 kamil