wireguard-openbsd/sys/nfs/nfs_socket.c, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/nfs/nfs_socket.c?h=jd%2Fqueueboosts2020-01-21T00:18:13Zsys/nfs: misc. tsleep(9) -> tsleep_nsec(9); ok mpi@2020-01-21T00:18:13Zchelohacheloha@openbsd.org2020-01-21T00:18:13Zurn:sha1:a600cd2797a115f98c314af7b17d336cc49523cdKeep socket timeout intervals in nsecs and use them with tsleep_nsec(9).2020-01-15T13:17:35Zmpimpi@openbsd.org2020-01-15T13:17:35Zurn:sha1:1a273344ae32a61ecc379c236ac9b23f6623257d
Introduce and use TIMEVAL_TO_NSEC() to convert SO_RCVTIMEO/SO_SNDTIMEO
specified values into nanoseconds. As a side effect it is now possible
to specify a timeout larger that (USHRT_MAX / 100) seconds.
To keep code simple `so_linger' now represents a number of seconds with
0 meaning no timeout or 'infinity'.
Yes, the 0 -> INFSLP API change makes conversions complicated as many
timeout holders are still memset()'d.
Inputs from cheloha@ and bluhm@, ok bluhm@
Convert infinite sleeps to tsleep_nsec(9).2019-12-05T10:41:57Zmpimpi@openbsd.org2019-12-05T10:41:57Zurn:sha1:ae991a59e6428f3b2827acac3fe1ff209967e1e5
ok jca@
When killing a process, the signal is handled by any thread that2019-05-13T19:21:31Zbluhmbluhm@openbsd.org2019-05-13T19:21:31Zurn:sha1:788422d65be41111bc05f25ec194535e3ae7eb6c
does not block the signal. If all threads block the signal, we
delivered it to the main thread. This does not conform to POSIX.
If any thread unblocks the signal, it should be delivered immediately
to this thread.
Mark such signals pending at the process instead of a single thread.
Then any thread can handle it later.
OK kettenis@ guenther@
M_LEADINGSPACE() and M_TRAILINGSPACE() are just wrappers for2018-11-09T14:14:31Zclaudioclaudio@openbsd.org2018-11-09T14:14:31Zurn:sha1:b5b7f62e3c22c1e16592be047f41a6fe57ed854d
m_leadingspace() and m_trailingspace(). Convert all callers to call
directly the functions and remove the defines.
OK krw@, mpi@
Instead of calculating the mbuf packet header length here and there,2018-09-10T16:14:07Zbluhmbluhm@openbsd.org2018-09-10T16:14:07Zurn:sha1:f02cb2e83cda2e7c843af31d86dd656fd741d8ab
put the algorithm into a new function m_calchdrlen(). Also set an
uninitialized m_len to 0 in NFS code.
OK claudio@
Use FNONBLOCK instead of SS_NBIO to check/indicate that the I/O mode2018-07-30T12:22:14Zmpimpi@openbsd.org2018-07-30T12:22:14Zurn: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@
Pass the socket to sounlock(), this prepare the terrain for per-socket2018-06-06T06:55:22Zmpimpi@openbsd.org2018-06-06T06:55:22Zurn:sha1:34bd5584fb2db3006ff476d7134486452e236076
locking.
ok visa@, bluhm@
nfs_connect() returns EINVAL at the beginning if nm_sotype is2017-09-07T11:35:34Zbluhmbluhm@openbsd.org2017-09-07T11:35:34Zurn:sha1:4d661fe08286eae646fd95cfaabd9d2efa55ef0a
invalid. But the compiler cannot know whether it has changed in
the meantime, so in the else case a bunch of variables would not
be initialized. Add a panic() there to change the compiler's
assumptions, the code should not be reached anyway.
found by clang -Wuninitialized; OK deraadt@
Preallocate option mbufs in order to reduce solock()/sounlock() dances.2017-09-05T08:02:48Zmpimpi@openbsd.org2017-09-05T08:02:48Zurn:sha1:b0c492408c1a7e230bd2412e9f4f7daa61b83eda
Finally protect the last `so_rcv' and `so_snd' accesses with the socket
lock.
ok visa@, bluhm@