| #
13ee68ef |
| 27-Jan-2025 |
christos <christos@NetBSD.org> |
Add getnameinfo files
|
| #
955f68aa |
| 26-Jan-2025 |
kre <kre@NetBSD.org> |
Correct a minor typo. s/sandboc/sandbox/
|
| #
466e8ade |
| 26-Jan-2025 |
christos <christos@NetBSD.org> |
sets changes for new bind-9.
|
| #
e0c6a19a |
| 23-Jan-2025 |
christos <christos@NetBSD.org> |
add new test
|
| #
9ab9c43b |
| 02-Jan-2025 |
kre <kre@NetBSD.org> |
Fix build after recent regex tests addition (make it be an addition, and don't forget tests/libtre)
|
| #
b248d216 |
| 01-Jan-2025 |
christos <christos@NetBSD.org> |
new regex test.
|
| #
faf3bea1 |
| 22-Dec-2024 |
riastradh <riastradh@NetBSD.org> |
t_time_arith: New test for timer calculations.
This will facilitate fixing various problems in the arithmetic to determine, given an itimer's scheduled time (it_value) and periodic interval (it_inte
t_time_arith: New test for timer calculations.
This will facilitate fixing various problems in the arithmetic to determine, given an itimer's scheduled time (it_value) and periodic interval (it_interval) along with the current time of actual expiry (now), what time the itimer should be rescheduled for (next, new value of it_timer) on the same clock.
Later we can also put tests for other functions like tvtohz here, and make them test many different values of hz/tick.
XXX Not 100% sure about all of these cases -- there is some room for reasonable discussion about what the right answer is. But we have unquestionably implemented the wrong thing for many of these cases, even if the answers this test checks for may not be quite right yet.
PR kern/58922: itimer(9): arithmetic overflow PR kern/58925: itimer(9) responds erratically to clock wound back PR kern/58926: itimer(9) integer overflow in overrun counting PR kern/58927: itimer(9): overrun accounting is broken
show more ...
|
| #
4cee645c |
| 17-Dec-2024 |
christos <christos@NetBSD.org> |
add a PT_KILL test.
|
| #
3bfaa971 |
| 16-Dec-2024 |
brad <brad@NetBSD.org> |
A driver for the MCP-2221 / 2221A multi-io chip. This is a USB to UART / GPIO / I2C multi-io chip probably based upon a programmed PIC. The end result is that simple gpio and i2c can exist on any sy
A driver for the MCP-2221 / 2221A multi-io chip. This is a USB to UART / GPIO / I2C multi-io chip probably based upon a programmed PIC. The end result is that simple gpio and i2c can exist on any system that provides a USB port. This is everything from a RPI to a Virtualbox VM.
o The UART presents itself as a umodem(4) device and pretty much works as one would expect.
o There are 4 simple GPIO pins with multiple functions that attach to gpio(4). Support for basic GPIO input and output exists with gpioctl, the ADC, DAC and clock pulse functions exist as ALT functions. For the ADC and DAC /dev/ devices are provided such that simple reads and writes interact with the ADC and DAC. The IRQ function on pin GP1 and bit banging the GPIO with gpiopps(4) and gpioow(4) are not really supported. The short answer is that a spin lock is held while trying to do USB transfers and that isn't allowed.
o There is a simple I2C engine that attaches to iic(4). This mostly works as expected, except that a READ without STOP is not supported by the engine which causes problems for some drivers. Most drivers do not seem to use READ without STOP and seem to work as expected. Support for changing the I2C speed is not supported, but nothing much really does that.
o A userland utility called umcpmioctl(8) is provided that allows the query of the status of the chip and allows for the query of the flash memory and the setting of some of the flash memory parameters mostly related to gpio. This utility interacts with a control device in /dev/. The flash memory contents is copied to the sram on boot up of the chip and can be used to adjust how the chip sets up the gpio pins, among other things. Support for setting or entering the chip password is not provided.
o A number of sysctls are provided to mess with various settings. These are detailed in the man page.
While not perfect, the chip is reasonable, cheap, and has at least one vendor making a breakout board. It is also one of the only ones in this space that has enough documentation to write a driver.
Support for a related chip, the MCP-2210, which provides SPI and GPIO may exist some day as the programming interface is very simular.
show more ...
|
| #
b48dffc9 |
| 10-Nov-2024 |
riastradh <riastradh@NetBSD.org> |
tests/kernel/t_cloexec: New tests for close-on-exec.
Verified that the following tests fail on a netbsd-10 kernel:
- clonedev_posixspawn - dup3_posixspawn - fcntldupfd_posixspawn
PR kern/58822: cl
tests/kernel/t_cloexec: New tests for close-on-exec.
Verified that the following tests fail on a netbsd-10 kernel:
- clonedev_posixspawn - dup3_posixspawn - fcntldupfd_posixspawn
PR kern/58822: close-on-exec is broken for dup3 and opening cloning devices
show more ...
|
| #
3ade096c |
| 02-Nov-2024 |
christos <christos@NetBSD.org> |
make zstd a private library (for now)
|
| #
7c5d5dfd |
| 30-Oct-2024 |
christos <christos@NetBSD.org> |
Hook zstd to the build and enable it for libarchive and file.
|
| #
e4f43b7b |
| 09-Oct-2024 |
kre <kre@NetBSD.org> |
Add a test for clock_nanotime() [ PR kern/58733 ]
Add a t_nanosleep test to the kernel tests, to (to a limited extent) validate its functionality.
Initially this concentrates on the issue from PR k
Add a test for clock_nanotime() [ PR kern/58733 ]
Add a t_nanosleep test to the kernel tests, to (to a limited extent) validate its functionality.
Initially this concentrates on the issue from PR kern/58733 where if a process paused in nanosleep() is stopped, and then continued, and if it is using TIMER_ABSTIME, the call will return prematurely, but indicating success.
There are (currently) 4 test cases, to test all 4 possibilities using CLOCK_MONOTONIC and CLOCK_REALTIME (if someone wants to add any other clocks that make sense, that should be easy) and TIMER_ABSTIME and TIMER_RELTIME.
Currently both TIMER_ABSTIME tests fail (the TIMER_RELTIME tests pass). When the kernel bug is fixed, the ABSTIME tests should be fixed along with it.
These tests are currently somewhat crude, and I'm not sure how well they will work on a qemu test system (they work as expected on bare metal).
show more ...
|
| #
fa6c0a34 |
| 03-Oct-2024 |
christos <christos@NetBSD.org> |
new semtimedop(2) GSoC 2024 (Shivraj Jamgade)
|
| #
131535b7 |
| 19-Sep-2024 |
gdt <gdt@NetBSD.org> |
tests: Add test for remquo
This test currently fails, because remquo has bugs. (A bugfix will be committed soon.) Test vectors derived from results from code by Charles Karney in GeodesicLib/proj,
tests: Add test for remquo
This test currently fails, because remquo has bugs. (A bugfix will be committed soon.) Test vectors derived from results from code by Charles Karney in GeodesicLib/proj, and manually inspected.
show more ...
|
| #
394db10a |
| 09-Sep-2024 |
riastradh <riastradh@NetBSD.org> |
math.h: Add math_errhandling, MATH_ERRNO, MATH_ERREXCEPT.
XXX Should maybe put a __math_errhandling in machine/math.h, but only VAX uses MATH_ERRNO and that's not likely to change any time soon, so
math.h: Add math_errhandling, MATH_ERRNO, MATH_ERREXCEPT.
XXX Should maybe put a __math_errhandling in machine/math.h, but only VAX uses MATH_ERRNO and that's not likely to change any time soon, so this will serve for now with less churn.
PR standards/56234: missing C99 frobs in <math.h>
show more ...
|
| #
66e07482 |
| 02-Sep-2024 |
ozaki-r <ozaki-r@NetBSD.org> |
distrib, etc: install shmif_pcapin and its tests
|
| #
0d283a3a |
| 27-Aug-2024 |
riastradh <riastradh@NetBSD.org> |
arc4random(3): Add automatic tests.
This verifies that: - arc4random zeroes its state and reseeds itself on fork - arc4random reseeds itself on entropy consolidation (e.g., VM clone) - arc4random fa
arc4random(3): Add automatic tests.
This verifies that: - arc4random zeroes its state and reseeds itself on fork - arc4random reseeds itself on entropy consolidation (e.g., VM clone) - arc4random falls back to global state if it can't allocate local state because address space limits cause mmap to fail
NOTE: This adds a new libc symbol __arc4random_global, but it's in the reserved namespace and only used by t_arc4random, so no libc minor bump.
PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork
show more ...
|
| #
9824ac6c |
| 18-Aug-2024 |
rin <rin@NetBSD.org> |
sets/lists: Make gdbserver MI by using MKGDBSERVER
|
| #
c4e44ee2 |
| 15-Aug-2024 |
riastradh <riastradh@NetBSD.org> |
libc: New functions c8rtomb(3) and mbrtoc8(3).
New in C23, for converting from UTF-8 to locale-dependent multibyte sequences (c8rtomb) or vice versa (mbrtoc8), along with the new type char8_t.
Cond
libc: New functions c8rtomb(3) and mbrtoc8(3).
New in C23, for converting from UTF-8 to locale-dependent multibyte sequences (c8rtomb) or vice versa (mbrtoc8), along with the new type char8_t.
Conditional on either: - _NETBSD_SOURCE - _ISOC23_SOURCE - __STDC_VERSION__ >= 202311L
(Riding the libc minor bump from this morning for the UTF-16/UTF-32 versions from C11.)
PR standards/58601: uchar.h C23 compliance: char8_t, mbrtoc8, c8rtomb
show more ...
|
| #
2cbd152a |
| 15-Aug-2024 |
riastradh <riastradh@NetBSD.org> |
libc: New C11 functions mbrtoc16, mbrtoc32, c16rtomb, c32rtomb.
The mbrtoc16/32 functions read mulitbyte strings according to the current locale into UTF-16/32 code unit sequences; the c16/32rtomb f
libc: New C11 functions mbrtoc16, mbrtoc32, c16rtomb, c32rtomb.
The mbrtoc16/32 functions read mulitbyte strings according to the current locale into UTF-16/32 code unit sequences; the c16/32rtomb functions write UTF-16/32 code unit sequences into multibyte strings according to the current locale. The `r' means restartable: they work incrementally and pick up where they left off.
NOTE: This bumps the libc minor version, since it adds new symbols.
PR lib/52374: <uchar.h> missing
show more ...
|
| #
cc1e5796 |
| 15-Aug-2024 |
riastradh <riastradh@NetBSD.org> |
uchar.h: New header file for C11 (and C++11) compliance.
Implementation of the new functions mbrtoc16, c16rtomb, mbrtoc32, and c32rtomb to come later. Updates for C23 to come later.
PR lib/52374:
uchar.h: New header file for C11 (and C++11) compliance.
Implementation of the new functions mbrtoc16, c16rtomb, mbrtoc32, and c32rtomb to come later. Updates for C23 to come later.
PR lib/52374: <uchar.h> missing
show more ...
|
| #
564557bb |
| 09-Aug-2024 |
bad <bad@NetBSD.org> |
add tests/kernel/t_umount.c: test case for unmount(2)
demonstrate that failing to umount and async mounted file system causes the kernel syncer to start flushing dirty buffers for it.
PR kern/58564
add tests/kernel/t_umount.c: test case for unmount(2)
demonstrate that failing to umount and async mounted file system causes the kernel syncer to start flushing dirty buffers for it.
PR kern/58564: async mounts revert to being synced after failed unmount
show more ...
|
| #
1672207d |
| 11-Jul-2024 |
riastradh <riastradh@NetBSD.org> |
Revert the duplication of compat set lists; do it another way.
1. Restore the compatdir and compatfile tags in base and debug.
=> compatdir marks directories that should have per-ABI compat
Revert the duplication of compat set lists; do it another way.
1. Restore the compatdir and compatfile tags in base and debug.
=> compatdir marks directories that should have per-ABI compat subdirectories, like /usr/lib having /usr/lib/o32 and /usr/lib/64 on mips64.
=> compatfile marks files that have per-ABI versions in the nearest compatdir, like /usr/lib/o32/libc.so.12.221.
This is the mechanism we use to avoid duplicating every library that has a compat version in multiple set lists.
2. Teach sets.subr to split the compatdir and compatfile entries out into separate sets for base and debug.
The mechanism is to internally use:
- a new tag `omitcompat' when processing base and debug, so we don't generate the per-ABI compat directories or per-ABI compat files under them;
- a new tag `takecompat=${ABI}' when processing base32/64 and debug32/64, so we _do_ generate the per-ABI compat directories for ${ABI}.
=> On, e.g., mips64, base32 uses `takecompat=o32' and base64 uses `takecompat=64'.
=> On, e.g., aarch64, base32 uses `takecompat=eabi,takecompat=eabihf', and there is no base64.
3. Record in sets.subr the list of `32' and `64' architectures for each port.
This is maybe not the right place to put it, but it's also not clear that we want to keep exactly this division -- maybe it would be more sensible to just have per-ABI , e.g.:
(aarch64) base-eabi, base-eabihf (amd64) base-i386 (mips64) base-o32, base-64 (mipsn64) base-o32, base-n32
But I'll leave cleaning that up for another day.
4. Adjust some sets. Mostly this commit shouldn't change what file go in what sets, but, e.g., on mips64, the following move from base32 to base64 as part of this change, which I think is appropriate:
- /lib/64 - /libexec/ld.elf_so-64 - /usr/lib/64 - /usr/libdata/debug/lib/64 - /usr/libdata/debug/usr/lib/64 - /usr/libexec/ld.elf_so-64
TBD: Remove ./lib and ./usr/lib from debug/mi; they're already in base/mi. Maybe move ./usr/libdata/debug to from base/mi to debug/mi.
This reverts most of the set list changes in:
https://mail-index.netbsd.org/source-changes/2024/04/09/msg150763.html
PR misc/58365
show more ...
|
| #
d7574629 |
| 09-Jul-2024 |
christos <christos@NetBSD.org> |
Add missing d
|