Age | Commit message (Collapse) | Author |
|
If rsize is NULL, do not update the variable. Otherwise the bootloader
will crash when it invokes libsa's fchmod().
This lets the bootloader work again after the recent loadrandom()
change. The fix should also improve the chances of sysupgrade(8) on
loongson.
Note that pmon_iostrategy() does not allow writing. fchmod() will fail
but does not prevent boot.
|
|
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.
|
|
minor changes.
|
|
This is the same change made in rev 1.21 to match the drm drivers.
It was reverted as Lucas Raab reported problems with inteldrm taking
over the fb with a 4k display. Lucas confirmed that this is no longer
an issue.
Prompted by a similar patch from John Carmack to raise the limits.
ok kettenis@
|
|
discussed with deraadt@
|
|
operations for ufs and ufs2 into the file_system[] array ...
|
|
(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...
ok kettenis
|
|
operations where appropriate. Based on a diff from deraadt@
ok deraadt@
|
|
|
|
(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 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.
|
|
ok kettenis
|
|
|
|
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@
|
|
howto
|
|
|
|
|
|
|
|
from John Carmack
|
|
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@
|
|
|
|
|
|
code in line with arm64.
ok deraadt@
|
|
|
|
|
|
|
|
inputs & ok kettenis@
|
|
miod@ agrees this can go
|
|
This lets the kernel detect retguard traps and send SIGABRT instead
of SIGEMT.
SIGEMT does not indicate correctly the nature of the error (stack
overflow, violation of control flow). It can confuse the user to restart
the program without further investigation.
Prompted by and OK deraadt@
OK mortimer@
|
|
|
|
These were removed from files.alpha 1.105 in 2017 and the rcons bits
they reference were removed in 2006.
removal suggested by miod@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|