<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/ddb, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/ddb?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/ddb?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-05-26T21:35:43Z</updated>
<entry>
<title>Stop requiring that .strtab has long alignment.</title>
<updated>2020-05-26T21:35:43Z</updated>
<author>
<name>gkoehler</name>
<email>gkoehler@openbsd.org</email>
</author>
<published>2020-05-26T21:35:43Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8529ee830f51fdf387a98463b8dce57fd3e9dd24'/>
<id>urn:sha1:8529ee830f51fdf387a98463b8dce57fd3e9dd24</id>
<content type='text'>
When ddb loads symbols, the .strtab contains char strings and doesn't
need long alignment.  Our bootloader provides long alignment, but I
started loading symbols on powerpc64 without our bootloader.

ok mpi@ guenther@ kettenis@
</content>
</entry>
<entry>
<title>Separate the stack trace saving interface from ddb. The saving does not</title>
<updated>2020-01-20T15:58:23Z</updated>
<author>
<name>visa</name>
<email>visa@openbsd.org</email>
</author>
<published>2020-01-20T15:58:23Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c59fd4de211d6138fc0156a4857079e64932ffe8'/>
<id>urn:sha1:c59fd4de211d6138fc0156a4857079e64932ffe8</id>
<content type='text'>
require the debugger on most architectures, and the separation makes the
code easier to use from other subsystems.

The function definitions are still conditional to DDB. However, that
should not matter for now.

OK deraadt@, mpi@
</content>
</entry>
<entry>
<title>If the kernel panics due to SMEP or SMAP, print correct stack trace</title>
<updated>2020-01-09T15:18:58Z</updated>
<author>
<name>bluhm</name>
<email>bluhm@openbsd.org</email>
</author>
<published>2020-01-09T15:18:58Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=f5ddcacac9da2465bbe02ae38b98b86373925c01'/>
<id>urn:sha1:f5ddcacac9da2465bbe02ae38b98b86373925c01</id>
<content type='text'>
and pass information to ddb.  This helps to debug kernel NULL pointer
function calls.
input guenther@; OK kettenis@
</content>
</entry>
<entry>
<title>Default to 0 arguments if no symbol has been found in the CTF section.</title>
<updated>2019-11-12T07:34:43Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-11-12T07:34:43Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=3998cbb6ead6fd258530a8c9248c3fbddd0ece94'/>
<id>urn:sha1:3998cbb6ead6fd258530a8c9248c3fbddd0ece94</id>
<content type='text'>
Symbols not present in the CTF data are generally assembly routines which
have either no argument or do not follow the ABI that the various MD stack
unwinders understand.

This makes ddb(4) trace simpler to understand.

ok jasper@
</content>
</entry>
<entry>
<title>db_addr_t -&gt; vaddr_t</title>
<updated>2019-11-07T13:16:25Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-11-07T13:16:25Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=08f058f85b93d7b0c2c1980be746a186c934fcf0'/>
<id>urn:sha1:08f058f85b93d7b0c2c1980be746a186c934fcf0</id>
<content type='text'>
ok deraadt@
</content>
</entry>
<entry>
<title>FALSE -&gt; 0, missed in previous.</title>
<updated>2019-11-07T10:51:46Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-11-07T10:51:46Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6b31bf08acae32cf9d16f792aa2796ace7893f46'/>
<id>urn:sha1:6b31bf08acae32cf9d16f792aa2796ace7893f46</id>
<content type='text'>
Spotted by deraadt@
</content>
</entry>
<entry>
<title>Substitute boolean_t/TRUE/FALSE by int/1/0.</title>
<updated>2019-11-06T07:30:08Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-11-06T07:30:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8383b4f2d10d7847749ab102afce1f16559c555c'/>
<id>urn:sha1:8383b4f2d10d7847749ab102afce1f16559c555c</id>
<content type='text'>
ok dlg@, jasper@, anton@
</content>
</entry>
<entry>
<title>Get rid of `ddb_is_active' instead use `db_active'.</title>
<updated>2019-07-20T23:06:51Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-07-20T23:06:51Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=cfc2cdf6e59832252c69d5dea5bafc064ba44bf3'/>
<id>urn:sha1:cfc2cdf6e59832252c69d5dea5bafc064ba44bf3</id>
<content type='text'>
From Christian Ludwig &lt;christian_ludwig at genua dot de&gt;

ok visa@
</content>
</entry>
<entry>
<title>Fix ddb not to write its history to out of the region.  When the</title>
<updated>2019-04-02T10:50:20Z</updated>
<author>
<name>yasuoka</name>
<email>yasuoka@openbsd.org</email>
</author>
<published>2019-04-02T10:50:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a99eef19e79dd15c8379393894bd0e55179d7978'/>
<id>urn:sha1:a99eef19e79dd15c8379393894bd0e55179d7978</id>
<content type='text'>
inputted line just ends at sizeof(db_history), ddb started writing the
histories to out of the region.  diff from IIJ.

ok deraadt anton
</content>
</entry>
<entry>
<title>remove prototype from earlier version of reboot code. spotted by anton</title>
<updated>2019-04-01T09:28:24Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2019-04-01T09:28:24Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8f50b3efa8225ac5a72c3283b45d807f133a6032'/>
<id>urn:sha1:8f50b3efa8225ac5a72c3283b45d807f133a6032</id>
<content type='text'>
</content>
</entry>
</feed>
