summaryrefslogtreecommitdiffstats
path: root/usr.bin/mandoc/man_html.c
diff options
context:
space:
mode:
authorstsp <stsp@openbsd.org>2020-02-12 16:02:51 +0000
committerstsp <stsp@openbsd.org>2020-02-12 16:02:51 +0000
commiteb93640f5e88d3a38d60d25998221f75b84cc369 (patch)
treec5419394906c0eb83093792fa2a3dd4d62ef8eaa /usr.bin/mandoc/man_html.c
parentCheck bogus values from interrupt in ict and non-ict case. r1 and r2 (diff)
downloadwireguard-openbsd-eb93640f5e88d3a38d60d25998221f75b84cc369.tar.xz
wireguard-openbsd-eb93640f5e88d3a38d60d25998221f75b84cc369.zip
Implement a workaround for missing Tx completion interrupts in iwm(4).
iwm(4) releases resources whenever hardware signals Tx completion for a frame at Tx queue index 'N'. It has been observed that we sometimes get an interrupt for frame 'N - 2' followed by an interrupt for frame 'N', with no interrupt being received for frame 'N - 1'. Whenever this occurred a later decision to roam to another AP would fail since AP node references for frames affected by missing interrupts were never released. Another side-effect was an mbuf leak. The problem was first observed at 36c3 and debugged there with bluhm@. ok tobhe@
Diffstat (limited to 'usr.bin/mandoc/man_html.c')
0 files changed, 0 insertions, 0 deletions