<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/nfs/nfs_node.c, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/nfs/nfs_node.c?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/nfs/nfs_node.c?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-01-20T23:21:55Z</updated>
<entry>
<title>struct vops is not modified during runtime so use const which moves each</title>
<updated>2020-01-20T23:21:55Z</updated>
<author>
<name>claudio</name>
<email>claudio@openbsd.org</email>
</author>
<published>2020-01-20T23:21:55Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=2d6b9e38f30a31b6aa3a85df5a94059bc694a80e'/>
<id>urn:sha1:2d6b9e38f30a31b6aa3a85df5a94059bc694a80e</id>
<content type='text'>
into read-only data segment.
OK deraadt@ tedu@
</content>
</entry>
<entry>
<title>Drop unnecessary `p' parameter from vget(9).</title>
<updated>2018-05-27T06:02:14Z</updated>
<author>
<name>visa</name>
<email>visa@openbsd.org</email>
</author>
<published>2018-05-27T06:02:14Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=08107a0b7d66fc523db27a131ca819e179fb022c'/>
<id>urn:sha1:08107a0b7d66fc523db27a131ca819e179fb022c</id>
<content type='text'>
OK mpi@
</content>
</entry>
<entry>
<title>Implement proper locking for NFS nodes.</title>
<updated>2018-05-05T11:54:11Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2018-05-05T11:54:11Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=53ae78e5c8685444295de5425173d1e56b3eae35'/>
<id>urn:sha1:53ae78e5c8685444295de5425173d1e56b3eae35</id>
<content type='text'>
Tested in bulks by many. ok visa@, beck@
</content>
</entry>
<entry>
<title>Clean up the parameters of VOP_LOCK() and VOP_UNLOCK(). It is always</title>
<updated>2018-04-28T03:13:04Z</updated>
<author>
<name>visa</name>
<email>visa@openbsd.org</email>
</author>
<published>2018-04-28T03:13:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=36bb23f12acb06197346657619c449dc8e0cae8e'/>
<id>urn:sha1:36bb23f12acb06197346657619c449dc8e0cae8e</id>
<content type='text'>
curproc that does the locking or unlocking, so the proc parameter
is pointless and can be dropped.

OK mpi@, deraadt@
</content>
</entry>
<entry>
<title>Change the representation of an NFS mount point by caching the root</title>
<updated>2018-04-09T09:39:53Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2018-04-09T09:39:53Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=94f656b1673b744d6034691e69f1e80e4217bfe1'/>
<id>urn:sha1:94f656b1673b744d6034691e69f1e80e4217bfe1</id>
<content type='text'>
nodes.

nfs_root() now returns a "locked" vnode, so vput(9) must be called to
release it.  Note that this has currently no effect as nfs_lock/unlock
are still stubs.

This will prevent some lock odering problems with upcoming NFSnode
locking.

Tested by landry@, sthen@, visa@, naddy@ and myself.

From NetBSD with some tweaks, ok visa@
</content>
</entry>
<entry>
<title>Check for possible race after sleeping instead of using a rwlock to</title>
<updated>2018-03-28T09:40:26Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2018-03-28T09:40:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ac2a721c191ba569ac6fef04503e89ce9a869936'/>
<id>urn:sha1:ac2a721c191ba569ac6fef04503e89ce9a869936</id>
<content type='text'>
protect insertions in `nm_ntree'.

This will prevent a future lock ordering problem with NFSnode's lock.

ok tedu@, visa@
</content>
</entry>
<entry>
<title>replace the use of RB macros with the RBT functions.</title>
<updated>2016-09-27T01:37:38Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2016-09-27T01:37:38Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=b78d9702d9d5bf5d9ee6b9126881a47c0fef6601'/>
<id>urn:sha1:b78d9702d9d5bf5d9ee6b9126881a47c0fef6601</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove the unused flags argument from VOP_UNLOCK().</title>
<updated>2016-03-19T12:04:15Z</updated>
<author>
<name>natano</name>
<email>natano@openbsd.org</email>
</author>
<published>2016-03-19T12:04:15Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=937fcae7c622e0ae47c1757467b994983f2677fb'/>
<id>urn:sha1:937fcae7c622e0ae47c1757467b994983f2677fb</id>
<content type='text'>
torture tested on amd64, i386 and macppc
ok beck mpi stefan
"the change looks right" deraadt
</content>
</entry>
<entry>
<title>sync a function's comment with its signature</title>
<updated>2016-02-09T00:56:04Z</updated>
<author>
<name>mmcc</name>
<email>mmcc@openbsd.org</email>
</author>
<published>2016-02-09T00:56:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=5fe8f27d792ae59dfdb3177ab39dfe449302d096'/>
<id>urn:sha1:5fe8f27d792ae59dfdb3177ab39dfe449302d096</id>
<content type='text'>
ok tedu@, with a slight tweak
</content>
</entry>
<entry>
<title>Remove some includes include-what-you-use claims don't</title>
<updated>2015-03-14T03:38:46Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2015-03-14T03:38:46Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=21dab745d772244ad59a415114e48be2888cfbc8'/>
<id>urn:sha1:21dab745d772244ad59a415114e48be2888cfbc8</id>
<content type='text'>
have any direct symbols used.  Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@
</content>
</entry>
</feed>
