| Commit message (Collapse) | Author | Files | Lines |
|
|
|
prompted by and ok jmc@
|
|
makes the test pass when invoked by doas.
|
|
a critical issue as the pointer back to the proc in the struct cpu_info
won't match, but it is better to avoid dangling pointers like this.
ok patrick@, drahn@
|
|
OK phessler@
|
|
SIG_ATOMIC_MAX for INTERNALSIG instead of
INT_MAX.
|
|
a lot of.
put the spam behind an ACPITHINKPAD_DEBUG define which can be used
when adding support for actually useful buttons.
previous version ok deraadt, phessler, and kettenis
|
|
|
|
by labelling dhclient routes. Just use
the route(8) logic when flushing routes.
ok benno@ claudio@
|
|
|
|
discussed with henning@
OK claudio@, benno@, job@
|
|
With i219V, it sometimes happens that em fails to attach with this error:
em0: Hardware Initialization Failed
em0: Unable to initialize the hardware
This happens always if booting native Windows 10 first and then rebooting into
openbsd without switching the laptop off. But it has also been seen in other
cases.
This change ports the e1000_disable_ulp_lpt_lp() logic from the FreeBSD driver
to disable ultra-low-power (ULP) mode. This seems to fix the problem in many
(but not all) cases.
The code has been merged in a way to make the diff from FreeBSD minimal. For
example, the SWFW register is called H2ME on newer chips, so a new define is
introduced. Also, the em_toggle_lanphypc_pch_lpt() function is left as separate
function even if only used in one place at the moment.
ok tom@
"commit it" deraadt@
|
|
the input file lacks useful debug sections).
adjust option handling accordingly to pass any flags not handled by
ctfstrip(1) down to strip(1).
help and ok mpi@ tb@
|
|
input benno, deraadt, tedu
also standardize on #if 0 since it makes tedu's editor vomit.
OK benno, pirofti on a previous version
|
|
when WITNESS is enabled
ok visa@ kettenis@
|
|
elsewhere
ok visa@ kettenis@
|
|
ok florian@ claudio@
|
|
OK guenther@
|
|
iwm_stop() sets the phy context pointer in the ic_bss node to NULL.
If iwm_stop() runs in parallel to the newstate task, the newstate task can
dereference this pointer in iwn_update_quotas() or iwm_binding_cmd().
So check the pointer for NULL before derefencing.
This is a quick and dirty workaround.
A proper fix for such task races is still pending.
|
|
ok kettenis@
|
|
memory garbage to the hardware while setting up beacon transmission.
The driver left some fields of a struct rt2661_tx_desc on stack uninitialized.
Zero out the entire struct before using it.
ok mpi@
|
|
the read accessors we don't have and fixing the prototypes - the
data type of each and every argument differs in the OpenSSL manuals.
Reference the new page from SSL_set_tmp_ecdh(3) as suggested by jsing@.
|
|
if a hypothetical and malicious USB device reports no Rx endpoints.
ok mpi@
|
|
iwm(4) firmware could cause an out of bounds read of the ic->ic_channels
array by lying about the channel a frame was received on. This array index
is now properly bounds-checked. Not an errata-worthy fix, since the firmware
has full DMA access anyway.
While here, I noticed another problem: Stop assigning a firmware-derived value
to ni->ni_chan. The Rx interrupt handler has no business tweaking that pointer.
ok mpi@
|
|
|
|
Feedback and OK jsing@.
|
|
Pointers from tb@
|
|
OK jsing.
|
|
|
|
It can set limits on different max-sessions if there're using several protocols
such as PPPoE and L2TP/IPsec.
ok yasuoka@
|
|
fatal firmware error debug output.
|
|
Clue provided by jca and claudio.
OK jca
|
|
it around.
OK jca
|
|
completely; previous behaviour would not prevent further options
appearing after the hostname (ssh has a supported options after the
hostname for >20 years, so that's too late to change).
ok deraadt@
|
|
private keys. The latter having the advantage of being supported
for no-OpenSSL builds; bz#2754 ok markus@
|
|
Ok benno@
|
|
Recommended by and discussed with many.
|
|
Ok benno@, jca@.
|
|
|
|
|
|
feedback and ok awhile ago bluhm@ job@
|
|
rk3399-firefly work in USB2 mode.
ok patrick@
|
|
ok mpi@ deraadt@
|
|
sigalgs.
|
|
back.
ok guenther@
|
|
hanging around to potentially invalid address space.
Discussed with beck@ and doug@
|
|
|
|
dname always.
|
|
|
|
calculate them as done for other objects
|