WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/nfs/nfsnode.h?h=jd%2Fqueueboosts 2019-01-21T18:09:21Z 2019-01-21T18:09:21Z anton anton@openbsd.org 2019-01-21T18:09:21Z urn:sha1:6bd4f7ca0ef936d4e355b60a534d1efc45dff893 structure allows for better tracking of pending lock operations which is essential in order to prevent a use-after-free once the underlying vnode is gone. Inspired by the lockf implementation in FreeBSD. ok visa@ Reported-by: syzbot+d5540a236382f50f1dac@syzkaller.appspotmail.com 2018-05-05T11:54:11Z mpi mpi@openbsd.org 2018-05-05T11:54:11Z urn:sha1:53ae78e5c8685444295de5425173d1e56b3eae35 Tested in bulks by many. ok visa@, beck@ 2009-12-15T15:53:48Z beck beck@openbsd.org 2009-12-15T15:53:48Z urn:sha1:482c7c115fdae33459bb8f2cb77f08dd95529322 picking a name meant that more than 58 sillys in a directory and we fail with EINVAL, resulting in strange problems for nfs which in turn causes pain and stress in building, and PTSD in nfs and vfs hackers. Has bit us in the butt since the vienna f2k7 hackathon. good suggestions from deraadt@ guenther@ and otto@ ok deraadt@,oga@,blambert@,krw@,guenther@, and a "very special ok" tedu@ Oh god, I'm an nfs hacker.. 2009-09-02T18:20:54Z thib thib@openbsd.org 2009-09-02T18:20:54Z urn:sha1:9c9522aef4377907b3328bfb62e786a97ac04324 problem noticed by deraadt@ ok beck@ 2009-08-27T23:26:56Z thib thib@openbsd.org 2009-08-27T23:26:56Z urn:sha1:00cb47382d7b1975afa6a1c047964d09dbaf54c8 and worked members. nad_worked becomes NFSAIOD_WAKEUP, which is set after if an aiod was removed from the idle list and woken up by nfs_asyncio(). don't rely on tsleep wchans being unique, that is keep going back to sleep if woken up unless the NFSAIOD_WAKEUP flag is set. fix a divide by zero crash if nfs.vfs.iothreads is set to 0, as that can happen when we recalculate the maximum buf's to queue up for each aiod. in nfs_asyncio() set the nad_mnt to NULL before returning the aiod back to the idle list in the case where we have already queued up to many bufs, otherwise we trip an assertion. minimize the time we are holding the nfs_aiodl_mtx to only when we are inserting or removing from the lists, with the exception of nfs_set_naiod() as it would make the loops more complicated and its uncommon in any case. tested by myself and deraadt@ "fine with me" deraadt@ 2009-08-26T12:08:10Z thib thib@openbsd.org 2009-08-26T12:08:10Z urn:sha1:7ae834763f3b211b20afc5742144def2ddb93829 before inserting it back into the list. crashes debugged with help from deraadt@ who also tested this fix. 2009-08-20T15:04:24Z thib thib@openbsd.org 2009-08-20T15:04:24Z urn:sha1:0324048376a3be805af0956efb4d721b44c78185 each mount, and when work is "found", peg an aiod to that mount todo the I/O. Make nfs_asyncio() a bit smarter when deciding when to do asyncio and when to force it sync, this is done by keeping the aiod's one two lists, an "idle" and an "all" list, so asyncio is only done when there are aiods hanging around todo it for us or are already pegged to the mount. Idea liked by at least beck@ (and I think art@). Extensive testing done by myself and jasper and a few others on various arch's. Ideas/Code from Net/Free. OK blambert@. 2009-08-10T10:59:11Z thib thib@openbsd.org 2009-08-10T10:59:11Z urn:sha1:e54eb321b579286ca3146523210a3e9c42962ae1 Idea from NetBSD. OK blambert@ 2009-01-24T23:30:42Z thib thib@openbsd.org 2009-01-24T23:30:42Z urn:sha1:c585412d3e2a158f3d8e11095e301311f1a49236 mtime, gives us better granularity, helps with cache consistency. Idea lifted from NetBSD. OK blambert@ 2009-01-19T23:40:36Z thib thib@openbsd.org 2009-01-19T23:40:36Z urn:sha1:fdc7e2e58d1bb00cdcc1be13de80732ae071c84a cache instead of setting n_attrstamp to 0 directly. Lift the macro name from NetBSD. prompted by and OK blambert@