stop trying to refuse a whole bunch of ioctls when securelevel > 1, which
was advertised as "pf filter and NAT rules may not be altered" - however,
there are numerous other ways, like turning pf of per-interface using set
skip, removing/adding interfaces from/to groups etc etc etc
root is root, period. pf doesn't have anything securelevel-dependent now.
"set skip" reported by acts1631kjv at proton
support deraadt, ok sashan claudio sthen
Remove sm_transactionid. This was originally intended to hook messages to
when sending requests to AgentX backends, but this functionality ended up
fully in application.c.
OK op@
devel/libnotify: check notify_get_server_info() return code and exit early if there's no notification daemon
silences vfprintf NULL messages when notify-send is run without dbus running.
ok ajacoutot@ (MAINTAINER)
Remove mrt6_mrouter_ver since it is unused and will never be used.
Our MRT6 code has no compat fallback for the old (> 25year) mrt6msg
format. We only use the fixed version with the alignment fix.
So there is no need to track mrt6_mrouter_ver since it is always MRT6_INIT
and that will never change. So burn this bridge for good.
OK bluhm@
fallback to PCI reset on x86
Attempt system reset with writes to a memory region used for PCI.
Both Intel and AMD document reset at the 0xcf9 address.
Adapted from FreeBSD by Gert-Jan Vons to fix reset on a
Fujitsu Futro S940.
ok deraadt@
Don't free the io queue memory when suspending, so it doesn't have to be
reallocated on resume. This removes a potential sleep point in the resume
path. The queue is still recreated on the controller, so its software state
has to be reset instead.
ok dlg@ deraadt@
Use nvme_ccb_get/put directly for queue create and delete commands.
These are issued in situations where we know all ccbs are on the free list,
and we wouldn't be able to sleep if they weren't, so going through the io
pool doesn't help.
ok dlg@ deraadt@
Take the kernel lock around pgo_refernce() call; not all of our uvm_object
implementations are mpsafe (in particular the vnode one). From Acts1631.
ok claudio@
Avoid using malloc(9) when walking lists of clocks, PHYs, mailboxes,
hardware locks and power domains. This helps avoiding sleeping in
DVACT_SUSPEND and DVACT_RESUME.
ok phessler@