tweak previous:
* make struct fuse_args argument name consistent
* change some ellipses into complete sentences
* add a missing word
* use .Vt for a type name
* use .Fa for struct member names
* use "or" instead of "and" below RETURN VALUES
* add the missing fuse_mount(3) below SEE ALSO
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.
productivity/baikal: add timezone workaround for recurrence expansion
As explained in [0], when creating a calendar via the web interface, Baikal
sets cal:calendar-timezone to a timezone string instead of a VTIMEZONE object.
This causes an issue when querying events with expanded recurrences, see [1].
To work around this, create a new DateTimeZone object from the string.
[0] https://github.com/sabre-io/Baikal/issues/1241
[1] https://github.com/sabre-io/Baikal/issues/1325