| Age | Commit message (Collapse) | Author |
|---|
|
MI boot.c's "a-x" fchmod on bsd.upgrade is the only caller that checks the
return value and that call can fail on, e.g. softraid volumes.
Stop clobbering the actual fchmod return value and get that warning printed.
OK deraadt
|
|
ok miod@ millert@
|
|
NetBSD dev_net.c rev 1.15 bootparam.c rev 1.19
https://mail-index.netbsd.org/source-changes/2009/10/21/msg002212.html
|
|
To appease the clang 15 warning -Wdeprecated-non-prototype (turned on
by -Wall). ok millert@
|
|
New warning -Warray-parameter is a bit overzealous.
ok millert@
|
|
If __builtin_ctzl() is used on sparc64, gcc 4.2 will emit a call to
__ctzdi2. For userland this is in libgcc or compiler-rt. In the kernel
we put these functions in libkern.
'looks good' deraadt@ miod@
|
|
is ELF" world. Eliminate use of them in amd64, arm64, armv7, i386,
macppc, mips64, and sparc64 code.
ok deraadt@ jca@ krw@
|
|
ok deraadt@
|
|
the final kernel symbol table.
Add END()s to match ENTRY()s.
ok deraadt@
|
|
uses, as the latter requires manual handling of _PROF_PROLOGUE.
Add END()s to match ENTRY()s.
ok deraadt@
|
|
From original commit message: To mitigate against spectre attacks,
AMD processors without the IBRS feature need an lfence instruction
after every near ret. See software techniques for managing speculation
on AMD processors revision 9.17.20 mitigation G-5.
ok deraadt@
|
|
is ELF" world. Eliminate use of them in m88k code.
ok aoyama@
|
|
Start eliminating it.
ok mpi@ mlarkin@ krw@
|
|
We're not maintaining a this as a fork, it's upstream source with a handful
of patches. Thus, the RCS ids aren't particularly useful or important. They
are a bit of a maintenance burden and generate noise in diffs.
ok kn, no objection millert, "kill" guess who
|
|
|
|
provide an explicit list of files to build in libsa.
|
|
bootblocks to shrink a little.
|
|
inline use was removed in 1998
|
|
libkern bzero doesn't have the 486 path but is otherwise the same
ok mlarkin@ deraadt@
|
|
|
|
|
|
Only boot-loader changes are needed. Both installboot(8) and
the kernel already do what is required to make this work.
ok kn@
Tested:
biosboot on vmm: kn, stsp
biosboot and efiboot on server hardware: stsp
|
|
The kernel source assumes the original zlib ABI. There is no reason to
stick to this local change. Pull in a fix matching ctfdump.c -r1.26.
This is hopefully the last change necessary to undo a painful hack that
was committed 19 years ago without ok. Someone owes me a lot of beer...
ok millert
|
|
|
|
on some older hardware, see https://github.com/madler/zlib/issues/613
Pointed out by tj and sthen
commit ec3df00224d4b396e2ac6586ab5d25f673caa4c2
Author: Mark Adler <madler@alumni.caltech.edu>
Date: Wed Mar 30 11:14:53 2022 -0700
Correct incorrect inputs provided to the CRC functions.
The previous releases of zlib were not sensitive to incorrect CRC
inputs with bits set above the low 32. This commit restores that
behavior, so that applications with such bugs will continue to
operate as before.
|
|
Build tests by myself for amd64 and arm64, sthen and inoguchi for i386
and gkoehler for macppc and powerpc64, thanks!
Detailed changelog is part of the committed diff.
|
|
ok mbuhl millert
|
|
Backport zlib fix for the multi line CLEAR_HASH macro. There is
an else branch where only half of the macro is executed conditionally.
Acording to upstream comment this has only little impact.
https://github.com/madler/zlib/commit/38e8ce32afbaa82f67d992b9f3056f281fe69259
ok bluhm (who had the same diff)
|
|
OK miod@
|
|
|
|
Found by LLVM scan-build.
OK millert@ deraadt@
|
|
writing to disk using the Open Firmware interfaces is buggy and causes
corruption of the disk. While it isn't entirely clear what versions
of Open Firmware are affected, but it seems to only affect IDE drives.
So if we detect an IDE drive, disable writing to it. This results in
a small lose of bootloader functionality (bsd.upgrade loop prevention
and flagging /etc/random.seed re-use) but that is better than losing
the ability to run OpenBSD at all.
Based on a diff by Ted Bullock (who did all the hard work of debugging
this and coming up with a viable fix).
ok deraadt@
|
|
to 3-term BSD license.
|
|
ok krw@, deraadt@
|
|
ok kettenis@
|
|
O_RDONLY rather using 0
ok beck
|
|
I should have used Byte (unsigned char) which led to passing twice the
correct size to free.
Found & tested by bluhm with the sys/netinet/ipsec tests on i386.
|
|
Rebased version of a diff from miod who described it as follows:
This tries to keep diffability against upstream, hence a questionable
choice of the size type for zcfree() - but all sizes should fit in 32
bits anyway.
Since all zcfree routines used in the tree cope with NULL arguments
(including the various alloc.c used by the boot blocks), I have
simplified TRY_FREE to compensate for the growth.
Reminded by and ok mpi
|
|
These library functions were added as stopgaps because GCC 4.2.1
lacks the corresponding __sync_* builtins on mips64. However,
the builtins are now provided by Clang.
|
|
option BUILDFIXED -- which is incompatible with kernel hibernate unpack since
it places side-effects into BSS, rather than inside z_streamp or using
the private allocator. While here DYNAMIC_CRC_TABLE could cause similar
problems, so disable this also.
Space savings for the media is best done with bootblock-specific libz
compile options, coming in the following commit.
ok tb mlarkin
|
|
|
|
|
|
made sense.
Tested in snaps for a few days. deraadt helped with fitting things on
floppies and jmatthew found a bug I introduced.
ok deraadt
|
|
|
|
|
|
|
|
|
|
|
|
At a minimum, amd64/i386 should now boot from 4TB GPT formatted disks.
More daddr32_t terminations with extreme prejudice to follow.
Tested by various, in snaps for a few days.
ok deraadt@
|
|
This changes RETGUARD_SETUP(ffs) to RETGUARD_SETUP(ffs, %r11, %r12)
and RETGUARD_CHECK(ffs) to RETGUARD_CHECK(ffs, %r11, %r12)
to show that r11 and r12 are in use between setup and check, and to
pick registers other than r11 and r12 in some kernel functions.
ok mortimer@ deraadt@
|
