WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/kern/vfs_init.c?h=jd%2Fqueueboosts 2019-12-26T13:30:54Z 2019-12-26T13:30:54Z bluhm bluhm@openbsd.org 2019-12-26T13:30:54Z urn:sha1:af9e00b9fc49063c85c8d77d702d181236103cf3 OK visa@ 2019-04-02T13:07:28Z visa visa@openbsd.org 2019-04-02T13:07:28Z urn:sha1:2861400ecbfdff6825314e1c3461615957ee810d obvious misconfigurations that cannot work. OK mpi@ tedu@ 2018-09-17T14:56:37Z visa visa@openbsd.org 2018-09-17T14:56:37Z urn:sha1:2a8e6c51f70d8aea8ab0b5351f5054af434ce93b Because loadable kernel modules are no longer, there is no need to register or unregister filesystem implementations at runtime. Remove vfs_register() and vfs_unregister(), and make vfsinit() call vfs_init routines directly. Replace the linked list of vfsconf structs with the vfsconflist[] array. OK mpi@ bluhm@ 2018-09-16T11:41:44Z visa visa@openbsd.org 2018-09-16T11:41:44Z urn:sha1:6d4b78c662d82b8af03c81f64c38fdba924e23b6 OK bluhm@ 2017-12-11T05:27:40Z deraadt deraadt@openbsd.org 2017-12-11T05:27:40Z urn:sha1:7efda1a11d8bf31499aa02da4d14eddf1b5293ae for blocks re-fetchable from the filesystem. However at reboot time, filesystems are unmounted, and since processes lack backing store they are killed. Since the scheduler is still running, in some cases init is killed... which drops us to ddb [noted by bluhm]. Solution is to convert filesystems to read-only [proposed by kettenis]. The tale follows: sys_reboot() should pass proc * to MD boot() to vfs_shutdown() which completes current IO with vfs_busy VB_WRITE|VB_WAIT, then calls VFS_MOUNT() with MNT_UPDATE | MNT_RDONLY, soon teaching us that *fs_mount() calls a copyin() late... so store the sizes in vfsconflist[] and move the copyin() to sys_mount()... and notice nfs_mount copyin() is size-variant, so kill legacy struct nfs_args3. Next we learn ffs_mount()'s MNT_UPDATE code is sharp and rusty especially wrt softdep, so fix some bugs adn add ~MNT_SOFTDEP to the downgrade. Some vnodes need a little more help, so tie them to &dead_vnops. ffs_mount calling DIOCCACHESYNC is causing a bit of grief still but this issue is seperate and will be dealt with in time. couple hundred reboots by bluhm and myself, advice from guenther and others at the hut 2016-09-15T02:00:16Z dlg dlg@openbsd.org 2016-09-15T02:00:16Z urn:sha1:1378bae268607a02c6648b2f5af62a452cd7f812 the ioff argument to pool_init() is unused and has been for many years, so this replaces it with an ipl argument. because the ipl will be set on init we no longer need pool_setipl. most of these changes have been done with coccinelle using the spatch below. cocci sucks at formatting code though, so i fixed that by hand. the manpage and subr_pool.c bits i did myself. ok tedu@ jmatthew@ @ipl@ expression pp; expression ipl; expression s, a, o, f, m, p; @@ -pool_init(pp, s, a, o, f, m, p); -pool_setipl(pp, ipl); +pool_init(pp, s, a, ipl, f, m, p); 2016-08-25T00:01:13Z dlg dlg@openbsd.org 2016-08-25T00:01:13Z urn:sha1:e091d7e694e21d531b4b611491076cd98290baec ok kettenis@ 2015-03-14T03:38:46Z jsg jsg@openbsd.org 2015-03-14T03:38:46Z urn:sha1:21dab745d772244ad59a415114e48be2888cfbc8 have any direct symbols used. Tested for indirect use by compiling amd64/i386/sparc64 kernels. ok tedu@ deraadt@ 2014-12-19T05:59:21Z tedu tedu@openbsd.org 2014-12-19T05:59:21Z urn:sha1:fbab5b6cdee93fd0818b09c6201db020bd35a0fd marker for which pools are not interrupt safe. ok dlg 2014-09-08T01:47:05Z guenther guenther@openbsd.org 2014-09-08T01:47:05Z urn:sha1:cf6677a65b386628719094fda053786604840618 months that I broke it before the 5.5 release. confirmed as not being required by ports by sthen@, ajacoutot@, dcoppa@