summaryrefslogtreecommitdiffstats
path: root/lib/libssl/ssl_both.c
diff options
context:
space:
mode:
authorstsp <stsp@openbsd.org>2017-01-28 16:01:36 +0000
committerstsp <stsp@openbsd.org>2017-01-28 16:01:36 +0000
commitd8e0f7e4d6c88da99b44119362fe09d34dadfbed (patch)
tree04eae71bdf414a4e963d25338951e6bd0562640e /lib/libssl/ssl_both.c
parentBack out make(obj) hack: it doesn't solve the problem entirely and may (diff)
downloadwireguard-openbsd-d8e0f7e4d6c88da99b44119362fe09d34dadfbed.tar.xz
wireguard-openbsd-d8e0f7e4d6c88da99b44119362fe09d34dadfbed.zip
Make mira cope with out-of-range single frame error rate (SFER) values.
These are either due to driver bugs or rounding errors in fixed point math but can be dealt with gracefully and don't occur often (only one instance of this problem has been reported in the wild so far). Turn related panics into debug printfs. With 'ifconfig athn0 debug' the kernel now prints notifications about out-of-range SFER values in dmesg. Compile a kernel with 'option MIRA_DEBUG' to get a dump of driver stats in dmesg as well. This change should prevent an undesirable panic reported by Peter Kay, though it does not actually address the root cause of the problem. ok tb@
Diffstat (limited to 'lib/libssl/ssl_both.c')
0 files changed, 0 insertions, 0 deletions