Make sure that the filterset passed along with other objects is present.
For communication with the parent the missing presence of a filter_set
is cause for a panic. This should just never happen. For messages from
bgpctl that are forwarded by the session engine things are more complex.
Make sure the filter_set was sent and only execute the command that
wraps this filter_set is present. If it is not there it may have been
filtered out because it is invalid and then the command depending on
this data should not be executed.
OK tb@
regress: Test vmmcall raises #UD
On AMD/SVM the hypervisor will inject #UD when userland tries to
execute the vmmcall instruction. Same holds for vmgexit which is
encode as "rep vmmcall".
On Intel/VMX vmmcall and vmgexit are invalid instructions, so the
CPU will raise #UD.
ok mlarkin@
regress: Test vmcall raises #UD
On Intel/VMX the hypervisor will inject #UD when userland tries to
execute the vmcall instruction.
On AMD/SVM vmcall is an invalid instruction, so the CPU will raise
ok mlarkin@
On newer hardware generations, no async events are enabled by default,
so explicitly enable the ones we're interested in.
tested by stsp@ as part of a larger diff
ok dlg@
Upgrade git-annex to 10.20260115 supporting ghc 9.10.3
Remove the docs from git-annex as new hackage versions miss them
There's no obvious place outside main git repository to get the docs.
OK kili@
Update matterhorn for ghc-9.10.3
Relax dependency bounds for brick, vty, vty-crossplatform, data-clist,
random, and aeson to support GHC 9.10.3. Update cabal.inc with new
dependency versions and regenerate distinfo.
Broken on aarch64 due to a version conflict in binary package. The
ghc-bundled .so takes precedence over the one in cabal build. It's
built against a different set of dependencies and some systems
don't exist.
OK kili@