Age | Commit message (Collapse) | Author |
|
a vforked child behave correctly. Have the parent in a vfork()
wait on a (different) flag in *its* process instead of the child
to prevent a possible use-after-free. When ktracing the child
return from a fork, call it rfork if an rthread was created.
ok blambert@
|
|
|
|
|
|
With current strategies to put memory in the ``correct'' place it isn't
needed. There's also the problem that it did not work on all machines,
failing completely on some and utterly breaking DMA. So just remove it.
If anyone needs it it will be in the Attic.
ok deraadt@
|
|
ok deraadt@
|
|
the top of the dma constraint range and panic if they are not.
ok deraadt@, thib@, oga@
|
|
|
|
|
|
Discussed and okay drahn@. Okay deraadt@.
|
|
|
|
mask out invalid bits to prevent a protect fault.
Original diff by joshe@; further feedback and ok kettenis@
|
|
BOOTBIOS_MAXSEC line.
ok deraadt@.
|
|
of them, as well as some other unused proc md_flags bits: MDP_COMPAT and
MDP_SYSCALL.
ok mikeb@
|
|
a global, a couple of parameters, and opening up possibility of
traversing much longer EBR lists without blowing the stack.
Make seach algorithm the same as used in kern/subr_disk.c by checking
all primary partitions in the MBR/EBR before moving to next EBR. This
makes it more likely that everybody finds the same OpenBSD partition.
Largely from a diff posted to tech@ by ucsavl.
|
|
the same as i386 version. No change to .o file except for the one
%lld -> %u format fix.
|
|
512-byte sectors) as some BIOSen get confused when we ask for sectors
higher up.
Uss u_int throughout the boot code to calculate sector addresses,
since 32 bits is enough to do 28 ^ 1 - 1 arithmetic. Add checks
for wraparound.
I can now install and boot from the 7th extended partition below
128GB.
Much feedback & guidance from deraadt@. Also from weingart@ on
BIOS io.
ok deraadt@ (less a couple of minor tweaks found in testing)
|
|
|
|
do 32-bit block spanning. If later on we get some that can/should do
64-bit, that can be done now using daddr64_t (but of course, we are taking
this step to finalize the daddr_t 64-bit conversion).
ok miod krw
|
|
Add missing __statement modifiers and correct %1 to %0 in the asm.
ok mikeb@, pirofti@, drahn@
|
|
be lied to by the BIOS about successfully reading data.
ok deraadt@ weingart@
|
|
Okay guenther@, millert@.
|
|
of the next EBR is relative to the start of the extended partition
described in the first MBR, not relative to the EBR specifying the
offset in its extended partition entry.
Clean up installboot -v output. Use daddr64_t for all sector numbers.
Not a complete fix, but better than what we had. More tweaks to
come.
Inspired by a diff and cluebat from uscav on tech@ a few weeks
ago.
Feedback from matthew@, weingart@.
ok deraadt@
|
|
ok ketttenis
|
|
in pxe.h.
ok deraadt@ sthen@
|
|
after every disklabel read or write. This keeps the DUID cache more
in sync with the physical world. De-syncing noted by drahn@ while
zapping disklabels with dd.
ok jsing@ deraadt@
|
|
holding locks, this is not allowed, and nobody has stepped up to fix this,
so better not lure people into using bluetooth devices.
|
|
|
|
this is not documented by Intel.
tested by henning on d525
|
|
softraid volumes. If installboot is run on a softraid volume, a fake
single inode FFS filesystem is constructed to contain boot(8). This is
then installed onto the softraid volume via the BIOCINSTALLBOOT ioctl.
biosboot(8) is then patched and installed onto each disk that is a member
of the softraid volume.
Joint work with otto@ who came up with the concept of constructing a fake
FFS filesystem and wrote the code to do so.
No objection from miod@
|
|
"doesn't hurt" deraadt@
|
|
|
|
contains key material (note, that is not true in all drivers... hence
not always neccessary)
discussed with mikeb
|
|
explicit_bzero() where required
ok markus mikeb
|
|
devices on AMD Family 0Fh processors.
|
|
advertised in the MCFG table, and fall back on the traditional method for
other busses. Fixes issue reported by henning@.
|
|
Enable athn at uhub on all USB 2.0 capable arches.
|
|
access to PCIe extended configuration space access on modern i386 and amd64
machines.
|
|
in some grief. Split this out.
From Vladimir Kirillov
|
|
ok guenther
|
|
print the "can't get bus clock" message. While there, adjust comments for
the i3/i5/i7 CPUs and include the relevant Xeon models. The Intel marketing
people seem to have less influence on the Xeon names, so they describe the
CPU generation much better.
ok marco@, deraadt@
|
|
x86_atomic_*_l(), and update the callers of all of those to use the
underlying x86_atomic_*_u32() functions that they were expecting anyway.
Whether the x86_atomic_*_ul() macros should be eliminated has been deferred.
ok kettenis@, tedu@
|
|
The i386 version was removed some time ago, so kill its declaration too.
ok tedu@ kettenis@
|
|
a physical address [more precisely, something suitable to pass to pmap_enter()'sphysical address argument].
This allows MI drivers to implement mmap() routines without having to know
about the pmap_phys_address() implementation and #ifdef obfuscation.
|
|
for it. This makes the netisr a real C function which will help further
development. No noticable performance change on i386 and amd64.
With input from kettenis@ and miod@ additional OKs mikeb@ and henning@
|
|
the hardware crypto accelerator land. This fixes aes-ni, via xcrypt,
glxsb(4), hifn(4), safe(4) and ubsec(4) drivers.
Original commit message by angelos:
Don't keep the last blocksize-bytes of ciphertext for use as the next
plaintext's IV, in CBC mode. Use arc4random() to acquire fresh IVs per
message.
with and ok deraadt, ok markus, djm
|
|
|
|
its better as a per arch MD define anyway. all default to MAXDSIZ as before.
|
|
802.11n USB devices.
These are FullMAC devices that require a firmware to operate;
see man page for details.
Great thanks to Brad for donating hardware.
Committed over the TRENDnet TEW-649UB.
ok deraadt@
|
|
the 64-bit output/input. On i386, this means that the 64-bit value is in
eax:edx, but on amd64 gcc this is not the case (might be a gcc bug, or might
be intentionally different and annoying?). The consequence is that amd64
errata were not always being matched (and then "corrected" using the magic
repair code). We need to compose/decompose the 64-bit value like the
un-locked msr functions do.
originally pointed out by ragge, ok kettenis jsg
|
|
booting off made up of a bunch of fields like adapter, controller,
disk, and partition offsets, plus a table of all the disks it can
see which includes this id and a checksum.
the kernel goes through and checksums the disks and then maps that
back to the id associated with that disk, and then compares some
of the fields in those ids against the boot disks id to figure out
which disk its on.
the problem is we overflow one of those fields (the disk id one).
since the other fields are set to 0 by the boot loader, this doesnt
really matter that much. however, since those fields are now
significant because of the overflow, we should compare them too.
this prevents sd16 being matched as the boot disk after sd0 on my
system with 25 disks attached.
ok krw@ weingart@
|