<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sbin/dumpfs, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sbin/dumpfs?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sbin/dumpfs?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-06-20T07:49:04Z</updated>
<entry>
<title>With filesystem having many cylinder groups and many inodes per cg the</title>
<updated>2020-06-20T07:49:04Z</updated>
<author>
<name>otto</name>
<email>otto@openbsd.org</email>
</author>
<published>2020-06-20T07:49:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=abbb35584eeb1f783012251d6de83bc7a1260d24'/>
<id>urn:sha1:abbb35584eeb1f783012251d6de83bc7a1260d24</id>
<content type='text'>
ncg * ipg calcualtion can overflow if signed types are used.  Move
to uint32_t for the relevant values. Aligned with FreeBSD changes.
Also make sure newfs refuses to create an fs with more that 2^32-1
inodes.  ok millert@
</content>
</entry>
<entry>
<title>Do not look for an FFS1 file system at SBLOCK_UFS2.  Doing so will</title>
<updated>2020-02-17T16:11:25Z</updated>
<author>
<name>otto</name>
<email>otto@openbsd.org</email>
</author>
<published>2020-02-17T16:11:25Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6965e1ead680cce09aef2c1cbafa51a02c18c4b6'/>
<id>urn:sha1:6965e1ead680cce09aef2c1cbafa51a02c18c4b6</id>
<content type='text'>
find the wrong super-block for file systems with 64k block size.
ok visa@
</content>
</entry>
<entry>
<title>When system calls indicate an error they return -1, not some arbitrary</title>
<updated>2019-06-28T13:32:41Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-06-28T13:32:41Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=df69c215c7c66baf660f3f65414fd34796c96152'/>
<id>urn:sha1:df69c215c7c66baf660f3f65414fd34796c96152</id>
<content type='text'>
value &lt; 0.  errno is only updated in this case.  Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
</content>
</entry>
<entry>
<title>Use pledge "disklabel" as needed.  The theory here is these tools become more</title>
<updated>2015-11-23T19:19:29Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2015-11-23T19:19:29Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e384f6efb1362a0010a16f79ac0fdd849ba6c5b9'/>
<id>urn:sha1:e384f6efb1362a0010a16f79ac0fdd849ba6c5b9</id>
<content type='text'>
resistant against memory correctup, if a corrupt filesystem is given to them.
ok krw
</content>
</entry>
<entry>
<title>Adjust &lt;sys/param.h&gt; comments regarding use of use of MAXFRAG, or</title>
<updated>2015-01-20T18:22:20Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2015-01-20T18:22:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=78eb0b7e750a8abce6d5bf75f3980c4936ee0c1c'/>
<id>urn:sha1:78eb0b7e750a8abce6d5bf75f3980c4936ee0c1c</id>
<content type='text'>
delete &lt;sys/param.h&gt; if now possible
ok guenther
</content>
</entry>
<entry>
<title>Replace &lt;sys/param.h&gt; with &lt;limits.h&gt; and other less dirty headers where</title>
<updated>2015-01-16T06:39:28Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2015-01-16T06:39:28Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=b9fc9a728fce9c4289b7e9a992665e28d5629a54'/>
<id>urn:sha1:b9fc9a728fce9c4289b7e9a992665e28d5629a54</id>
<content type='text'>
possible.  Annotate &lt;sys/param.h&gt; lines with their current reasons.  Switch
to PATH_MAX, NGROUPS_MAX, HOST_NAME_MAX+1, LOGIN_NAME_MAX, etc.  Change
MIN() and MAX() to local definitions of MINIMUM() and MAXIMUM() where
sensible to avoid pulling in the pollution.  These are the files confirmed
through binary verification.
ok guenther, millert, doug (helped with the verification protocol)
</content>
</entry>
<entry>
<title>Nuke another pointless dev_bsize variable always set to 512 and use</title>
<updated>2014-05-13T12:51:40Z</updated>
<author>
<name>krw</name>
<email>krw@openbsd.org</email>
</author>
<published>2014-05-13T12:51:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6783a1e5c4321b7182fbd5db4161dfd0c82d01b1'/>
<id>urn:sha1:6783a1e5c4321b7182fbd5db4161dfd0c82d01b1</id>
<content type='text'>
DEV_BSIZE. David Vasek says it still works the same on 4K-byte-sector
device. i.e.  prints one value incorrectly. For which a fix should
be following soon.
</content>
</entry>
<entry>
<title>Use a time_t variable with ctime()</title>
<updated>2013-04-02T03:05:37Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2013-04-02T03:05:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=f5bbe9b4ff5bd6f8551a42c3df7c1d42d4ec2d2b'/>
<id>urn:sha1:f5bbe9b4ff5bd6f8551a42c3df7c1d42d4ec2d2b</id>
<content type='text'>
ok deraadt@
</content>
</entry>
<entry>
<title>switch open(...) to opendev(...)</title>
<updated>2011-02-28T00:12:19Z</updated>
<author>
<name>halex</name>
<email>halex@openbsd.org</email>
</author>
<published>2011-02-28T00:12:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=324d848ac3d2c1ce5cd78a43d0a46b45784d4733'/>
<id>urn:sha1:324d848ac3d2c1ce5cd78a43d0a46b45784d4733</id>
<content type='text'>
makes yet another utility honor DUID's

ok jsing@ miod@ deraadt@
</content>
</entry>
<entry>
<title>rcsid[] and sccsid[] and copyright[] are essentially unmaintained (and</title>
<updated>2009-10-27T23:59:19Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2009-10-27T23:59:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=043fbe51c197dbbcd422e917b65f765d8b5f8874'/>
<id>urn:sha1:043fbe51c197dbbcd422e917b65f765d8b5f8874</id>
<content type='text'>
unmaintainable).  these days, people use source.  these id's do not provide
any benefit, and do hurt the small install media
(the 33,000 line diff is essentially mechanical)
ok with the idea millert, ok dms
</content>
</entry>
</feed>
