qwx: update ni_rssi from ACK frame RSSI in tx completion
The hardware reports ack_rssi in the tx completion status when data
frames are acknowledged. Update ni_rssi with this value so ifconfig
reports accurate signal strength from the data path.
Like Linux ath11k, check WMI_TLV_SERVICE_HW_DB2DBM_CONVERSION_SUPPORT
to determine if the value is already in dBm or needs noise floor
adjustment. ACK frames may be sent with higher power than beacons,
providing a more accurate RSSI reading during active data transfer.
ok stsp@
Implement a ddb stop command that sends a SIGSTOP to the specified pid.
SIGSTOP can never be caught or ignored so there is no need for any
tricks to make sure the signal makes it. So this may work better in
cases where exiting a process may be too harsh.
OK kettenis@
In server_read_httpchunks() do not blindly enable the bufferevent.
This leads to a use-after-free since the bev->readcb() call could free
the memory holding the bev right before the bufferevent_enable() call.
Reported by Pontus Stenetorp.
from clauio@; OK florian@ rsadowski@
this is errata/7.7/019_httpd.patch.sig
In server_read_httpchunks() do not blindly enable the bufferevent.
This leads to a use-after-free since the bev->readcb() call could free
the memory holding the bev right before the bufferevent_enable() call.
Reported by Pontus Stenetorp.
from clauio@; OK florian@ rsadowski@
this is errata/7.8/013_httpd.patch.sig
In server_read_httpchunks() do not blindly enable the bufferevent.
This leads to a use-after-free since the bev->readcb() call could free
the memory holding the bev right before the bufferevent_enable() call.
Reported by Pontus Stenetorp.
OK florian@ rsadowski@
Break sorting out into a common file so formats and modes use the same
code. Also add -O for sorting to the list commands. From Dane Jensen in
GitHub issue 4813.
improve pf_find_state lookups by checking the direction of the states.
if we have the state from the packet coming into the stack we can
ensure the state we look up goes in the opposite direction.
use pf_states to link mbufs/inpcbs and forwarded connections together
this replaces the links between pf_state_keys and mbufs/inpcbs.
pf_states represent the actual connection tracked by pf, while
pf_state_keys are more general since they only contain the network
addresses. the fact that pf_state_keys exist is an implementation
detail in pf rather than a fundamentally useful artifact to the
rest of the system. the preference would have been to link things
to pf_states rather than pf_state_keys in the first place, but there
wasn't enough machinery (eg, refcounts and immutable links to
pf_state_keys) on pf_states to link to them directly. this means
pf still had to iterate over the states hanging off the pf_state_keys
to get to the actual pf_state it needed anyway.
discussed with henning@
ok sashan@ jmatthew@
have state and source limiter state cleanup assert on the right lock.
state and source limiters and they pf state links they're wired up
with are protected by the pf lock, not the pf state lock. this is
asserted correctly when setting up source and state limiters, but
i copy and pasted the wrong assert for the cleanup code.
this should fix the spurious "splassert: pf_create_state: want 1 have 0"
messages i get on my firewalls.
Update Spleen kernel fonts to version 2.2.0, bringing the following
improvements:
- Fix less-than sign alignment in the 12x24 version
- Fix right curly bracket alignment in the 12x24 version
- Fix right parenthesis alignment in the 32x64 version
openssl asn1pars: avoid a few unnecessary casts
If str is a const unsigned char * rather than a char *, we can get away
with a single cast and do not need to cast away const either. Reduce the
scope of tmpbuf and ctmpbuf (now p) while there.
ok kenjiro
EVP_SealInit.3: fix RETURN VALUES section
While normal calls return 0 for error and npubk for success, there is a
case where it returns the usual 1/0 thing. Make that explicit.
Prompted by a report by Niels Dossche
ok jsing kenjiro
