wireguard-openbsd/sys/isofs/udf, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/isofs/udf?h=jd%2Fqueueboosts2020-01-20T23:21:55Zstruct vops is not modified during runtime so use const which moves each2020-01-20T23:21:55Zclaudioclaudio@openbsd.org2020-01-20T23:21:55Zurn:sha1:2d6b9e38f30a31b6aa3a85df5a94059bc694a80e
into read-only data segment.
OK deraadt@ tedu@
Convert struct vfsops initializer to C99 style.2019-12-26T13:28:49Zbluhmbluhm@openbsd.org2019-12-26T13:28:49Zurn:sha1:41f642fce20c4c96fc6c5130f38d534763576904
OK visa@
vinvalbuf(9): tlseep -> tsleep_nsec(9); ok millert@2019-07-25T01:43:20Zchelohacheloha@openbsd.org2019-07-25T01:43:20Zurn:sha1:a8d7c3beb68e1470bb5980be2ef07ac9b9f618fcDrop unnecessary `p' parameter from vget(9).2018-05-27T06:02:14Zvisavisa@openbsd.org2018-05-27T06:02:14Zurn:sha1:08107a0b7d66fc523db27a131ca819e179fb022c
OK mpi@
Remove proc from the parameters of vn_lock(). The parameter is2018-05-02T02:24:55Zvisavisa@openbsd.org2018-05-02T02:24:55Zurn:sha1:6e880534696d274aaeeac6af7c28cedec17384cf
unnecessary because curproc always does the locking.
OK mpi@
Clean up the parameters of VOP_LOCK() and VOP_UNLOCK(). It is always2018-04-28T03:13:04Zvisavisa@openbsd.org2018-04-28T03:13:04Zurn:sha1:36bb23f12acb06197346657619c449dc8e0cae8e
curproc that does the locking or unlocking, so the proc parameter
is pointless and can be dropped.
OK mpi@, deraadt@
Use RWL_IS_VNODE with locks that are acquired through VOP_LOCK(),2018-03-28T16:34:28Zvisavisa@openbsd.org2018-03-28T16:34:28Zurn:sha1:d78cb2ffdac0b6a8690a0d0268283287e63c9871
to appease WITNESS. ext2fs and ffs already use the flag. The same
locking pattern appears with other file systems too, so this patch
addresses the remaining cases.
OK mpi@
Syncronize filesystems to disk when suspending. Each mountpoint's vnodes2018-02-10T05:24:23Zderaadtderaadt@openbsd.org2018-02-10T05:24:23Zurn:sha1:976e983900b26f1c1815971efe0ad0990654d735
are pushed to disk. Dangling vnodes (unlinked files still in use) and
vnodes undergoing change by long-running syscalls are identified -- and
such filesystems are marked dirty on-disk while we are suspended (in case
power is lost, a fsck will be required). Filesystems without dangling or
busy vnodes are marked clean, resulting in faster boots following
"battery died" circumstances.
Tested by numerous developers, thanks for the feedback.
In uvm Chuck decided backing store would not be allocated proactively2017-12-11T05:27:40Zderaadtderaadt@openbsd.org2017-12-11T05:27:40Zurn: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
If you use sys/param.h, you don't need sys/types.h2017-09-08T05:36:51Zderaadtderaadt@openbsd.org2017-09-08T05:36:51Zurn:sha1:b27348b2082c02cb5227e0e4933400ad6739ec5a