Age | Commit message (Collapse) | Author |
|
|
|
(fchmod +T by bootcode, chmod 600 by /etc/rc). If the seed is reused, and
HWRNG isn't available, the kernel won't get RB_GOODSEED indication...
|
|
here, and alternatively would need to rewind). WRITE code exists, but was
always wrong -- it writes the cache-buffer to disk, rather than the provided
write-buffer. Copy the write-buffer into the cache, and invalidate the cache
completely so that future reads start from scratch.
|
|
If loadrandom() succeeds, set RB_GOODRANDOM in boothowto.
To enable fchmod(), disk_open() has to mount the filesystem in writable
mode. This is tricky because the filesystem might be unclean. Hence the
code has to use MNT_FORCE.
Input and OK deraadt@
|
|
Load the kernel image from the filesystem upfront in rdboot and pass
the loaded image to octboot(4)'s kexec call in a memory buffer. As a
result, octboot(4) does not rely on a mounted filesystem.
OK deraadt@
|
|
|
|
This does not switch to newer firmware yet. The driver currently fails to
send frames when -48 firmware is used. And the -48 firmware image is not
yet available in fw_update(1).
|
|
This command doesn't seem to be needed with the ax200 device we currently
support. But it does not hurt and will be needed for other devices this
driver intends to support in the future.
ok mpi@
|
|
The iwx(4) driver intends to disable bluetooth. The command we sent to the
firmware says "wifi only", but also enabled a bluetooth module. This seems
to work as intended but is ambiguous. Linux also leaves all modules disabled
in wifi-only mode. So do not enable any BT modules in the BT_COEX command.
ok mpi@
|
|
station table. The Tx flush operation depends on the station being present.
Avoids a fatal firmware error when the driver moves out of AUTH state.
|
|
Some firmware versions don't expect LMAC_5G_INDEX in the binding command.
Set that value under the same conditions as the Linux driver does, which
makes this command work on -48 firmware.
ok mpi@
|
|
Newer iwx(4) firmware versions will require a larger beacon filter command.
The extra fields fields are initialized to zero even on Linux but newer
firmware will require a size change anyway.
ok mpi@
|
|
This will make mutex spinning time visible in top(1), and also might
improve stability.
The major change in this is that the old assembly code acquires
mutexes with an atomic exchange operation, but releases them with a
regular store, but the new code always uses atomic exchange
operations.
The mutex.h changes to the macros conform to <sys/mutex.h> to be able
to reset the system while in ddb.
Suggested from Miod Vallat, tested by me. The stability in heavy load
is greatly improved in my case.
|
|
Some drivers, such as ral(4), cannot provide the IV required for a replay
check because hardware strips the IV before passing the frame to the driver.
Which means frames with the RXI_HWDEC flag but without the 'protected' bit
set in the frame header must be passed without any further verification and
without updating the last-seen packet number.
All we can do is hope that these devices perform replay checking correctly.
Fixes a regression where some ral(4) devices would fail to receive packets
on encrypted networks. Reported and fix confirmed by Hendrik Meyburgh.
ok mpi@
|
|
|
|
Missed in previous.
|
|
From Vitaliy Makkoveev.
|
|
Premature locking is causing more trouble than it is solving issue. In this
case the lifetime of descriptors is protected by the KERNEL_LOCK() so using
a rwlock for the lookup introduce sleeping points and possible new races
without benefit.
From Vitaliy Makkoveev.
|
|
where the network stack indicates they're needed.
deraadt@ confirms this version doesn't break nfs over udp
ok dlg@
|
|
from Tero Koskinen
|
|
|
|
from Tero Koskinen
|
|
instead of hand-rolling the same code to set up a temporary ChaCha
instance.
tweak/ok semarie@, ok deraadt@
|
|
ok kettenis
|
|
sthen@ has reported that the patch might be causing hangs with X.
|
|
|
|
relax the fstat() check because the system will have left the file
in the right mode.
ok visa kettenis
|
|
sure that an old bootloader can boot a new kernel and a new bootloader
can still boot an old kernel some hackery is needed as old kernels check for
an exact size of the openbsd_bootdata struct.
tested (with softraid) by kn@
ok stsp@, deraadt@
|
|
ok kettenis
|
|
will frantically compensate.
ok kettenis
|
|
howto
|
|
|
|
|
|
|
|
from John Carmack
|
|
kcov_exit().
|
|
Tested on Yeeloong.
Looks good to miod@
|
|
Looks good to miod@
|
|
OK deraadt@
|
|
The data are static but they introduce differences between systems.
OK deraadt@
|
|
|
|
|
|
the Yeelong Lemote mips-based netbook. Kernel bits only for now, needs
polishing; most of this work done during h2k9 last month, although the
porting effort started earlier this year.
|
|
the Yeelong Lemote mips-based netbook. Kernel bits only for now, needs
polishing; most of this work done during h2k9 last month, although the
porting effort started earlier this year.
|
|
miod explained it was initially a long as it was thought drivers may
need to allocate storage but in practice they don't need more than
32 bits for an attribute.
suggested and reviewed by miod@
|
|
Suggested by John Carmack. miod agrees a rename would make sense and
explained it was initially thought drivers may need to allocate storage
but in practice they don't need more than 32 bits for an attribute.
ok mpi@
|
|
ok kettenis@, visa@
|
|
backout until resolved.
|
|
|
|
|