<feed xmlns='http://www.w3.org/2005/Atom'>
<title>netbsd/share/man, branch trunk</title>
<subtitle>NetBSD fork for lockdoc analysis</subtitle>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/'/>
<entry>
<title>versioningsyscalls(9): markup fixes</title>
<updated>2023-07-09T00:29:49+00:00</updated>
<author>
<name>uwe</name>
<email>uwe@NetBSD.org</email>
</author>
<published>2023-07-09T00:29:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=181b9dcc45c808ca8128cd520e72e056ee0b1a81'/>
<id>181b9dcc45c808ca8128cd520e72e056ee0b1a81</id>
<content type='text'>
While here, fix the pasto for the new ino_t and time_t size.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
While here, fix the pasto for the new ino_t and time_t size.</pre>
</div>
</content>
</entry>
<entry>
<title>Document how system call versioning is done. From this summer's compat-linux</title>
<updated>2023-07-08T16:14:11+00:00</updated>
<author>
<name>christos</name>
<email>christos@NetBSD.org</email>
</author>
<published>2023-07-08T16:14:11+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=0c94267aac509280cb2c98f1d9bf1bdc09759a3c'/>
<id>0c94267aac509280cb2c98f1d9bf1bdc09759a3c</id>
<content type='text'>
GSoC, by Theodore Preduta.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
GSoC, by Theodore Preduta.</pre>
</div>
</content>
</entry>
<entry>
<title>curcpu_stable(9): New function for asserting curcpu() is stable.</title>
<updated>2023-07-08T13:59:05+00:00</updated>
<author>
<name>riastradh</name>
<email>riastradh@NetBSD.org</email>
</author>
<published>2023-07-08T13:59:05+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=81aaded24099f3685918bea8bbfc0fa5d60ab781'/>
<id>81aaded24099f3685918bea8bbfc0fa5d60ab781</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>heartbeat(9): markup fixes</title>
<updated>2023-07-07T15:56:31+00:00</updated>
<author>
<name>uwe</name>
<email>uwe@NetBSD.org</email>
</author>
<published>2023-07-07T15:56:31+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=377d235d69183cc57f02e6f92fccba9b2daec941'/>
<id>377d235d69183cc57f02e6f92fccba9b2daec941</id>
<content type='text'>
Use .Cd for options.  Don't use the usual &lt;space&gt;&lt;tab&gt;, which is
superfluous in the man page.  Paragraph break after the config section
of synopsis, before the C API section.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Use .Cd for options.  Don't use the usual &lt;space&gt;&lt;tab&gt;, which is
superfluous in the man page.  Paragraph break after the config section
of synopsis, before the C API section.</pre>
</div>
</content>
</entry>
<entry>
<title>heartbeat(9): Fix grammaro in man page.</title>
<updated>2023-07-07T13:19:30+00:00</updated>
<author>
<name>riastradh</name>
<email>riastradh@NetBSD.org</email>
</author>
<published>2023-07-07T13:19:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=f1356aafe5a7dcd6c4611c38bae76cfc09267d1b'/>
<id>f1356aafe5a7dcd6c4611c38bae76cfc09267d1b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Replace main(9) reference with code location</title>
<updated>2023-07-07T13:15:00+00:00</updated>
<author>
<name>wiz</name>
<email>wiz@NetBSD.org</email>
</author>
<published>2023-07-07T13:15:00+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=9e86afd54a3f8db9ed241a99d586f0b19a6ad30d'/>
<id>9e86afd54a3f8db9ed241a99d586f0b19a6ad30d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Sort SEE ALSO</title>
<updated>2023-07-07T12:59:45+00:00</updated>
<author>
<name>wiz</name>
<email>wiz@NetBSD.org</email>
</author>
<published>2023-07-07T12:59:45+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=bbd31dd13cf4e1f7712e94b466050e87feac2299'/>
<id>bbd31dd13cf4e1f7712e94b466050e87feac2299</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>heartbeat(9): New mechanism to check progress of kernel.</title>
<updated>2023-07-07T12:34:49+00:00</updated>
<author>
<name>riastradh</name>
<email>riastradh@NetBSD.org</email>
</author>
<published>2023-07-07T12:34:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=de09df2fbee768e9082e19034d75860393b1d8c7'/>
<id>de09df2fbee768e9082e19034d75860393b1d8c7</id>
<content type='text'>
This uses hard interrupts to check progress of low-priority soft
interrupts, and one CPU to check progress of another CPU.

If no progress has been made after a configurable number of seconds
(kern.heartbeat.max_period, default 15), then the system panics --
preferably on the CPU that is stuck so we get a stack trace in dmesg
of where it was stuck, but if the stuckness was detected by another
CPU and the stuck CPU doesn't acknowledge the request to panic within
one second, the detecting CPU panics instead.

This doesn't supplant hardware watchdog timers.  It is possible for
hard interrupts to be stuck on all CPUs for some reason too; in that
case heartbeat(9) has no opportunity to complete.

Downside: heartbeat(9) relies on hardclock to run at a reasonably
consistent rate, which might cause trouble for the glorious tickless
future.  However, it could be adapted to take a parameter for an
approximate number of units that have elapsed since the last call on
the current CPU, rather than treating that as a constant 1.

XXX kernel revbump -- changes struct cpu_info layout</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This uses hard interrupts to check progress of low-priority soft
interrupts, and one CPU to check progress of another CPU.

If no progress has been made after a configurable number of seconds
(kern.heartbeat.max_period, default 15), then the system panics --
preferably on the CPU that is stuck so we get a stack trace in dmesg
of where it was stuck, but if the stuckness was detected by another
CPU and the stuck CPU doesn't acknowledge the request to panic within
one second, the detecting CPU panics instead.

This doesn't supplant hardware watchdog timers.  It is possible for
hard interrupts to be stuck on all CPUs for some reason too; in that
case heartbeat(9) has no opportunity to complete.

Downside: heartbeat(9) relies on hardclock to run at a reasonably
consistent rate, which might cause trouble for the glorious tickless
future.  However, it could be adapted to take a parameter for an
approximate number of units that have elapsed since the last call on
the current CPU, rather than treating that as a constant 1.

XXX kernel revbump -- changes struct cpu_info layout</pre>
</div>
</content>
</entry>
<entry>
<title>mk.conf(5): document rump variables</title>
<updated>2023-07-05T16:40:33+00:00</updated>
<author>
<name>lukem</name>
<email>lukem@NetBSD.org</email>
</author>
<published>2023-07-05T16:40:33+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=1a56dc243916e9eba8e116d8e3ab663c850d4666'/>
<id>1a56dc243916e9eba8e116d8e3ab663c850d4666</id>
<content type='text'>
Update mk.conf(5) with the rump variables from
- lib/librumpuser/README.compileopts
- sys/rump/README.compileopts

Add cross-references back to mk.conf(5) in those files.

Ensure that the Default: is listed last in a description,
for consistency with the convention in this file.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Update mk.conf(5) with the rump variables from
- lib/librumpuser/README.compileopts
- sys/rump/README.compileopts

Add cross-references back to mk.conf(5) in those files.

Ensure that the Default: is listed last in a description,
for consistency with the convention in this file.</pre>
</div>
</content>
</entry>
<entry>
<title>rc.conf(5): Set entropy=wait by default.</title>
<updated>2023-06-30T21:44:09+00:00</updated>
<author>
<name>riastradh</name>
<email>riastradh@NetBSD.org</email>
</author>
<published>2023-06-30T21:44:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.infra.scholz.ruhr/netbsd/commit/?id=04d6489017a0b0f710fc2a3205ab92e4b769497d'/>
<id>04d6489017a0b0f710fc2a3205ab92e4b769497d</id>
<content type='text'>
We no longer block indefinitely -- if nothing else, the hardclock
timer should yield enough samples to unblock /dev/random on all but
the most severely deterministic machines -- so it should be generally
safe for availability to set entropy=wait.

This doesn't guarantee that HWRNG/seed has been provided before you
run ssh-keygen or call getentropy(3) in a user application, but it
does raise the security above netbsd&lt;=9.

PR security/55659
PR lib/56905

XXX pullup-10</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We no longer block indefinitely -- if nothing else, the hardclock
timer should yield enough samples to unblock /dev/random on all but
the most severely deterministic machines -- so it should be generally
safe for availability to set entropy=wait.

This doesn't guarantee that HWRNG/seed has been provided before you
run ssh-keygen or call getentropy(3) in a user application, but it
does raise the security above netbsd&lt;=9.

PR security/55659
PR lib/56905

XXX pullup-10</pre>
</div>
</content>
</entry>
</feed>
