summaryrefslogtreecommitdiffstats
path: root/usr.bin/tmux/window-buffer.c
diff options
context:
space:
mode:
authorstsp <stsp@openbsd.org>2020-05-16 11:26:51 +0000
committerstsp <stsp@openbsd.org>2020-05-16 11:26:51 +0000
commit45e80987b74c7ed21276b4c7f6ddd93086eb7302 (patch)
tree740bb34b80170f67033db822749aaf2cd47c346c /usr.bin/tmux/window-buffer.c
parentDon't attempt to reset the state of the flip-flop associated with the (diff)
downloadwireguard-openbsd-45e80987b74c7ed21276b4c7f6ddd93086eb7302.tar.xz
wireguard-openbsd-45e80987b74c7ed21276b4c7f6ddd93086eb7302.zip
Fix PHY_CONTEXT commands sent to iwx(4) firmware.
iwx(4) firmware understands two different variants of these commands. Both variants are documented with the same command API version number, but they use different sizes for an embedded struct which contains information about channels. Which variant to use depends on whether the firmware advertises support for the "ULTRA_HB_CHANNELS" feature. The code I wrote to handle both cases had a bug in case this feature is not supported: The channel info size difference was only accounted for while computing the command's length, but not while writing command data. This bug does not affect devices presently matched by iwx(4). But it is possible that other devices may need this fix in the future. So, for now, fix the buggy code path instead of removing it. ok mpi@
Diffstat (limited to 'usr.bin/tmux/window-buffer.c')
0 files changed, 0 insertions, 0 deletions