daily CVS update output

2022-05-31 Thread NetBSD source update
Updating src tree: P src/bin/sh/memalloc.c P src/distrib/sets/lists/comp/mi P src/distrib/sets/lists/debug/mi P src/distrib/sets/lists/tests/mi P src/doc/HACKS P src/external/lgpl3/gmp/dist/longlong.h P src/games/gomoku/Makefile P src/include/limits.h P src/include/unistd.h P src/lib/libc/gen/Mak

Automated report: NetBSD-current/i386 build success

2022-05-31 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2022.06.01.00.50.24 mrg src/sys/modules/acpiverbose/pci.h,v 1.1 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2022.06.html#202

Automated report: NetBSD-current/i386 build failure

2022-05-31 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2022.05.31.20.28.57. An extract from the build.sh output follows: # compile vmt/vmt.o /tmp/build/2022.05.31.2

Re: kernel deadlock on fstchg with vnd

2022-05-31 Thread Michael van Elst
campbell+netbsd-current-us...@mumble.net (Taylor R Campbell) writes: >This would need to be integrated into autoconf/specfs to avoid races >in config_pseudo_spawn, sc->sc_configured, and config_pseudo_unspawn, vnd is peculiar in that it spawns a unit whenever it is opened and removes it again whe

Re: kernel deadlock on fstchg with vnd

2022-05-31 Thread Taylor R Campbell
> Date: Mon, 30 May 2022 14:33:42 +0200 > From: "J. Hannken-Illjes" > > >> 1767 /* Nuke the vnodes for any open instances */ > >> 1768 for (i = 0; i < MAXPARTITIONS; i++) { > >> 1769 mn = DISKMINOR(device_unit(vnd->sc_dev), i); > >> 1770 vde