| Age | Commit message (Collapse) | Author |
|---|
|
|
|
happens regardless.
Add a third one to only disregard base libraries
|
|
allows me to redefine methods to not do a thing
(maybe this will migrate to its own file if it grows enough)
|
|
|
|
|
|
and just say that instead of a dauntingly long list of packages
|
|
|
|
|
|
|
|
behaviour in accordance with man page. Introduce '-v' option to make
output more verbose.
Do a little refactoring to make code more consistent with other daemons
like ospfd(8), httpd(8), relayd(8), etc.
Feedback from bluhm benno
ok bluhm
|
|
|
|
|
|
|
|
bgpctl before calling strlcpy() with that string.
OK tb@ some long time ago
|
|
If installing firmware with `make install` from a port, it doesn't register
properly by adding "@option firmware" to the packing list, this means we ignore
that it is installed and reinstall it over and over with the registration
ending up in a tmpdir named directory inside the existing directory in
/var/db/pkg.
Unfortunately I don't know of a good way to automatically clean up from that,
so we just print a message after installing the actual firmware.
Reported by job@
No complaints about the patch on tech@ for several weeks.
|
|
Otherwise the exit status depends on whether we kept any firmware.
Reported by Brian Conway <bconway () rcesoftware ! com>
The clean solution suggested by guenther@
|
|
Previously if you did: fw_update otus-firmware-1.0p1.tgz
and that firmware didn't exist in the current directory,
we would download that firmware into the current directory.
Which is not the expected outcome.
|
|
The logging output from vmd(8) often specifies the function performing
the logging, but leaves which vm or vm device to guesswork and
reading tea leaves.
Change the logging formatting to prefix with information about the
specific vm and potentially the device subprocess. Most of this
logging is behind the "verbose" mode, but for warnings this will
clarify which vm or device logged the warning.
The format of vm/<name>/<device><index> is chosen to be concise and
less ugly than other approaches. This adjusts the process naming
for devices to match, dropping the use of brackets.
In the process of this change, updating log settings dynamically
via vmctl(8) is fixed by properly broadcasting that information to
the device subprocesses. The "vmm" process also now updates its own
state properly, so settings survive vm reboots.
ok mlarkin@
|
|
When vcpu threads pause, they are holding the run mutex lock. If
the event thread is asked to assert an irq on the pic and interrupts
are pending, it will try to take the run mutex lock on the vcpu.
This deadlocks.
Release the lock in the vcpu thread before waiting on the pause
condition variable.
ok mlarkin@
|
|
The previous commit used suboptimal variable names for ease of review.
Fix this up now.
ok claudio
|
|
An upcoming diff requires the ability to convert ASIdentifiers and
IpAddrBlocks into rpki-client's internal structures. Accordingly,
split already existing code into dedicated parsing functions . The
original functions now only extract the extension-specific data from
the X509_EXTENSION.
input/ok claudio
|
|
This will be needed by an upcoming feature where we will need to know
what trust anchor a given cert chains to. This doesn't change anything
except the size of the diff.
ok claudio job
|
|
OK tb@
|
|
Some log messages incorrectly said "vionet" or "vioblk". Fix based
on the context.
|
|
Some guests cause a warning message during a shutdown. Log the vmd
vm id and not the kernel vmm id as it's next to useless to the end
user. This has annoyed me too much.
|
|
|
|
|
|
OK mpi@
|
|
|
|
Upstream LLVM decided to drop the -dc flag and keep its -d alias for
some time:
https://github.com/llvm/llvm-project/commit/0688b00fc39fe87ec6dd3d37a732d067ff487f16
So this is only a workaround to let us update llvm to a recent release.
We'll probably need another fix not so distant future. Another approach
would be to just drop -dc from the linker invocation, and use
cc -fno-common when building instbin with base-gcc (already the default
with base-clang). But this approach needs more testing than I can
provide, as deraadt@ feared it would break in subtle ways.
ld -d compat alias pointed out by robert@, ok robert@
|
|
The original version of the virtio block device dynamically allocated
buffers to hold intermediate data when reading or writing to the
underlying disk fd(s). Since vioblk drivers may chain multiple
segments together, this leads to overly complex logic and on
read(2)/write(2) call per data segment.
Additionally, the virtio block logic in vmd didn't handle segments
that weren't block aligned (e.g. 512 bytes). If a guest provided
unaligned segments, garbage will be read or written.
Since virtio descriptors mimic iovec structures, this changes vmd's
device emulation to use that model. (This is how other hypervisors
emulate virtio devices.) This allows for zero-copy semantics using
iovec's, reducing memcpy and multiple read/write syscalls per io
transaction.
Testing by phessler@ and mlarkin@. OK mlarkin@.
|
|
|
|
|
|
|
|
Somehow missed in previous, regression reported by anton@.
|
|
OK tb@
|
|
|
|
It is now possible to save and print immutable arrays as below:
..$t = (1, 42, "something");
..printf("%d %s\n", $t.1, $t.2);
Also add support for evaluating builtin in order to save them in variables
(required by tuples)
|
|
avp_enum() checks if avp->length is valid.
ok mvp
|
|
This cherry-picks upstream git commit
0ee44ef384593ed0382d1ce6048d5a9c9440b45c.
Issue reported by landry@, which could be traced back to a buggy WiFi
driver that would constantly return ENOBUFS. This in turn lead
unwind(8) enter a tight loop through poll / sendto without making any
progress and burning 100% cpu.
OK sthen
|
|
radiusd module interface. This makes additional modules can modify
RADIUS request or response messages. Also add new "radius_standard"
module which uses this new feature, provides some generic features
like "strip-atmark-realm" which removes the realm part from the
User-Name attribute. from IIJ.
|
|
|
|
In prep for fixing some vioblk device issues, simplify the ioinfo
struct by dropping members that aren't needed.
ok mlarkin@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
introduced by the diff/patch process I use to avoid stomping on the local
changes in updates)
|
