<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/arch/amd64/include/tcb.h, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/amd64/include/tcb.h?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/amd64/include/tcb.h?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2017-10-13T05:14:02Z</updated>
<entry>
<title>I was one bit off in the "is canonical" test for FS.base (TCB pointer) values,</title>
<updated>2017-10-13T05:14:02Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2017-10-13T05:14:02Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ab07a1674255d38deb4192a7087a6b9972a47e3a'/>
<id>urn:sha1:ab07a1674255d38deb4192a7087a6b9972a47e3a</id>
<content type='text'>
so it was still possible to fault the kernel.

Problem observed by Maxime Villard
ok deraadt@ bluhm@
</content>
</entry>
<entry>
<title>amd64 needs FS.base values (the TCB pointer) to be validated, as noncanonical</title>
<updated>2017-09-27T05:43:55Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2017-09-27T05:43:55Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c742113d8903fcfb365128bb071fbbed675ee0d4'/>
<id>urn:sha1:c742113d8903fcfb365128bb071fbbed675ee0d4</id>
<content type='text'>
addresses will cause a fault on load by the kernel.

Problem observed by Maxime Villard
ok kettenis@ deraadt@
</content>
</entry>
<entry>
<title>TCB_GET_MEMBER() is no longer used after the TIB changes</title>
<updated>2016-09-04T08:49:35Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2016-09-04T08:49:35Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=96b8842b622f9505c1b9cc4ddf5b9b4045994781'/>
<id>urn:sha1:96b8842b622f9505c1b9cc4ddf5b9b4045994781</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Do lazy update/reset of the FS.base and %[def]s segment registers: reseting</title>
<updated>2015-05-18T19:59:27Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2015-05-18T19:59:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=b13138f26d8f4e65100b2377aab2ba4570a8d014'/>
<id>urn:sha1:b13138f26d8f4e65100b2377aab2ba4570a8d014</id>
<content type='text'>
segment registers in cpu_switchto if the old thread had made it to userspace
and restoring FS.base only on first return to userspace since context switch.

ok mlarkin@
</content>
</entry>
<entry>
<title>Oh yeah, a cvs id is good</title>
<updated>2011-10-19T06:48:56Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2011-10-19T06:48:56Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=f5501f3dfbb33536743d16aea10c06ce40a052e0'/>
<id>urn:sha1:f5501f3dfbb33536743d16aea10c06ce40a052e0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>"TLS-lite": add kernel support for a per-thread userspace pointer,</title>
<updated>2011-10-15T23:35:29Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2011-10-15T23:35:29Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6bb855475d0cdbaa6e89d93537105bdf30f02caf'/>
<id>urn:sha1:6bb855475d0cdbaa6e89d93537105bdf30f02caf</id>
<content type='text'>
for pointing to the thread-control-block.  Support for mapping this
to the correct hardware register can be added as it's finished;
start with support for amd64, sparc, and sparc64.  Includes syscalls
for getting and setting it (for a portable __errno implementation) as
well as creating a new thread with an initial value for it.

discussed with miod@, kettenis@, deraadt@; committing to get the syscalls
in with the impending libc bump and do further refinements in tree
</content>
</entry>
</feed>
