wireguard-openbsd/sys/kern/sys_socket.c, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/kern/sys_socket.c?h=jd%2Fqueueboosts 2020-02-22T11:58:29Z In preparation for unlocking ioctl(2), grab the kernel lock as needed. 2020-02-22T11:58:29Z anton anton@openbsd.org 2020-02-22T11:58:29Z urn:sha1:60e616d4462a6e14a239d984c6c9a30c8c69bf3b ok kettenis@ mpi@ visa@ Unify handling of ioctls FIOSETOWN/SIOCSPGRP/TIOCSPGRP and 2020-01-08T16:27:40Z visa visa@openbsd.org 2020-01-08T16:27:40Z urn:sha1:36b1b8b4dfaf3411193c17c2462937014292f2df FIOGETOWN/SIOCGPGRP/TIOCGPGRP. Do this by determining the meaning of the ID parameter inside the sigio code. Also add cases for FIOSETOWN and FIOGETOWN where there have been TIOCSPGRP and TIOCGPGRP before. These changes allow removing the ID translation from sys_fcntl() and sys_ioctl(). Idea from NetBSD OK mpi@, claudio@ Constify instances of struct fileops. 2020-01-05T13:46:02Z visa visa@openbsd.org 2020-01-05T13:46:02Z urn:sha1:c02bfb27cf5527eb0816ec39aad4db3ad4345c8c OK anton@, mpi@, bluhm@ Utilize sigio with sockets. 2018-11-19T13:15:37Z visa visa@openbsd.org 2018-11-19T13:15:37Z urn:sha1:e22141d5ca3312610ade1c4dcf8713b7639f70a5 OK mpi@ Reorder checks in the read/write(2) family of syscalls to prepare making 2018-08-20T16:00:22Z mpi mpi@openbsd.org 2018-08-20T16:00:22Z urn:sha1:2bd648c0c791046970147cb6db731832ad511740 file operations mp-safe. This change makes it clear that `f_offset' is only accessed in vn_read() and vn_write(), which will help taking it out of the KERNEL_LOCK(). This refactoring uncovered a race in vn_read() which is now documented and will be addressed in a later diff. ok visa@ Use FNONBLOCK instead of SS_NBIO to check/indicate that the I/O mode 2018-07-30T12:22:14Z mpi mpi@openbsd.org 2018-07-30T12:22:14Z urn:sha1:4a4dc3ea4c4158dccd297c17b5ac5a6ff2af5515 for sockets is non-blocking. This allows us to G/C SS_NBIO. Having to keep the two flags in sync in a mp-safe way is complicated. This change introduce a behavior change in sosplice(), it can now always block. However this should not matter much due to the socket lock being taken beforhand. ok bluhm@, benno@, visa@ Move socket & pipe specific logic in their ioctl handler. 2018-07-10T08:58:50Z mpi mpi@openbsd.org 2018-07-10T08:58:50Z urn:sha1:30cae0e11a68544aad56fe31465ffb5607069c7a ok visa@, tb@ Pass the socket to sounlock(), this prepare the terrain for per-socket 2018-06-06T06:55:22Z mpi mpi@openbsd.org 2018-06-06T06:55:22Z urn:sha1:34bd5584fb2db3006ff476d7134486452e236076 locking. ok visa@, bluhm@ Remove solock() surrounding PRU_CONTROL in soo_ioctl(). 2018-04-26T10:45:45Z pirofti pirofti@openbsd.org 2018-04-26T10:45:45Z urn:sha1:443bca7307a1df482d6d2b2a713dd4caf4d284b7 We do not need the lock there. Missed this in my former commit pushing NET_LOCK() down the stack. Found the hard way by naddy@, sorry! OK mpi@. Convert 'struct fileops' definitions to C99. 2018-04-10T09:17:45Z mpi mpi@openbsd.org 2018-04-10T09:17:45Z urn:sha1:e7e081a56a3695c910889f20cba3aa8b6127c262 ok millert@, deraadt@, florian@