WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/nfs?h=master 2021-03-11T13:31:35Z 2021-03-11T13:31:35Z jsg jsg@openbsd.org 2021-03-11T13:31:35Z urn:sha1:b66b9ef836b4335d57b8481be6faf1a0b9b7e205 2021-01-19T19:35:59Z mvs mvs@openbsd.org 2021-01-19T19:35:59Z urn:sha1:acd193d7816dd605086be131658f784274e3bec2 ok dlg@ 2021-01-02T02:41:42Z cheloha cheloha@openbsd.org 2021-01-02T02:41:42Z urn:sha1:cab22b2ba59f8fd0350f9c5c01a5d1f4579b64af We can simulate the current behavior without lbolt by sleeping for 1 second on the &nowake channel. ok mpi@ 2020-12-25T12:59:51Z visa visa@openbsd.org 2020-12-25T12:59:51Z urn:sha1:9b0cf67b268a857fffa6a742ad6be57acdc35301 Rename klist_{insert,remove}() to klist_{insert,remove}_locked(). These functions assume that the caller has locked the klist. The current state of locking remains intact because the kernel lock is still used with all klists. Add new functions klist_insert() and klist_remove() that lock the klist internally. This allows some code simplification. OK mpi@ 2020-09-27T17:25:19Z matthieu matthieu@openbsd.org 2020-09-27T17:25:19Z urn:sha1:8f51e4cc4562ba274cd7b5d02b277dc392651adb valid valuse of tv_sec but an invalid value for tv_nsec. Noticed by guenther@. ok beck@ deraadt@ 2020-09-27T16:40:44Z matthieu matthieu@openbsd.org 2020-09-27T16:40:44Z urn:sha1:d0ef113717f830052e3f8ccd22b9a09b2773fe06 timestamps. This issue was iscovered after rsync 3.2 changed behaviour on an NFS mounted partition.. Change lifted from NetBSD (r 1.204). ok beck@, kn@, deraadt@ 2020-08-24T10:02:07Z mvs mvs@openbsd.org 2020-08-24T10:02:07Z urn:sha1:f812a5316fbc19b14c154e5d79031dc4b58a4457 we expected. Remove the `else' path from nfs_boot_init(). If `nfsbootdevname' is not set something goes wrong and this is the panic condition. Also we exclude the case where we can get `ifp' which we don't expect. OK mpi@ 2020-06-24T22:03:40Z cheloha cheloha@openbsd.org 2020-06-24T22:03:40Z urn:sha1:3209772dfcc3950dd5df01bc44eebf75e637511e time_second(9) and time_uptime(9) are widely used in the kernel to quickly get the system UTC or system uptime as a time_t. However, time_t is 64-bit everywhere, so it is not generally safe to use them on 32-bit platforms: you have a split-read problem if your hardware cannot perform atomic 64-bit reads. This patch replaces time_second(9) with gettime(9), a safer successor interface, throughout the kernel. Similarly, time_uptime(9) is replaced with getuptime(9). There is a performance cost on 32-bit platforms in exchange for eliminating the split-read problem: instead of two register reads you now have a lockless read loop to pull the values from the timehands. This is really not *too* bad in the grand scheme of things, but compared to what we were doing before it is several times slower. There is no performance cost on 64-bit (__LP64__) platforms. With input from visa@, dlg@, and tedu@. Several bugs squashed by visa@. ok kettenis@ 2020-06-11T09:18:43Z mpi mpi@openbsd.org 2020-06-11T09:18:43Z urn:sha1:1c57bd6bc2d4b1536ac76e1cdb4ba92124a01e2a While here prefix kernel-only EV flags with two underbars. Suggested by kettenis@, ok visa@ 2020-06-08T08:04:09Z mpi mpi@openbsd.org 2020-06-08T08:04:09Z urn:sha1:6e29a9444098b33c28a7ce5b32b593b9539d7294 Adapt FS kqfilters to always return true when the flag is set and bypass the polling mechanism of the NFS thread. While here implement a write filter for NFS. ok visa@