Age | Commit message (Collapse) | Author |
|
Soon to be used by pyro(4) as well.
|
|
that they're implemented consistently in bounds_check_with_label().
Also, per krw's request, change bounds_check_with_label() to return 0
if the checks succeed, and change the drivers to test == -1 instead of
<= 0. (Man page update to follow; intentionally omitting
arch/vax/mba/hp.c from this commit because it doesn't even build
currently and miod@ promises to kill it soon.)
ok krw@
|
|
ok matthew@ tedu@
|
|
FREF()/FRELE() in lseek() so our struct file doesn't disappear in the
mean time.
Incorporating suggestions from tedu@ and guenther@; ok guenther@
|
|
|
|
also, rmpage updates curpage, no need to do it twice.
ok art deraadt guenther
|
|
the same, ok'd with IFQ_PURGE with happens to break on altq kernels by
claudio, ryan and bluhm
|
|
|
|
and not IFQ_IS_EMPTY, the former doesn't get overloaded with altq-specific
stuffz. original oks from claudio and ryan and bluhm, i take the liberty
to assume the oks for this fixed version
|
|
|
|
ok beck deraadt
|
|
the issue in our kernel was the broadcast address calculated on the /31
caused a ton of checks for use of broadcast addresses to kick in and
prevent one of the two addresses on the /31 from being used.
this diff basically detects if a /31 has been configured and doesnt
configure a broadcast address for it, which makes the ips usable
for normal traffic.
i wrote this so i could interoperate with "carrier" network gear
better, and sthen wants it so he can conserve address space use.
the further special casing of broadcast address handling was from claudio@
ok claudio@ markus@ sthen@ henning@
|
|
ironlake interrupt handler is changed. some nasty bug lurks in here,
and any binary change randomly exposes this and screws up the chip.
back this out for now; until it is found.
ok oga
|
|
biglock in mi_switch and just check if we're holding the biglock.
The idea is that the first entry point into the kernel uses KERNEL_PROC_LOCK
and recursive calls use KERNEL_LOCK. This assumption is violated in at
least one place and has been causing confusion for lots of people.
Initial bug report and analysis from Pedro.
kettenis@ beck@ oga@ thib@ dlg@ ok
|
|
delete.
|
|
These will be used to replace scsi_link's adapter_buswidth and luns
fields, but for now we stay compatible with existing SCSI adapter
driver conventions while I update them to set the scsibus_attach_args
fields directly.
ok dlg@
|
|
long" for __off_t. This is a C++ ABI bump, but martynas@ already
bumped libstdc++.
Discussed and requested by many on icb.
|
|
show useful info in systat io instead of goo
|
|
again makes assumptions of the ifqueue internals, ok ryan claudio
|
|
and that it is nul terminated. This means the longest path is now 103
char longs. With and OK guenther@
|
|
something. Doesn't matter right now because scsibus_attach_args only
has one field and it's mandatory, but I'm planning to move some more
fields from scsi_link to scsibus_attach_args+scsibus_softc.
ok dlg@
|
|
it was done for pf_headers in pf.c.
ok mcbride@ henning@
|
|
the header address in the mbuf.
ok henning@
|
|
ok claudio@
|
|
needs either of them.
ok krw@
|
|
place it was missing. Delete now redundant calls to DIOCGDINFO when
getting physical disk info in disklabel(8) and fdisk(8).
Reminded by a fdisk discussion with Andres Perera on tech@.
ok deraadt@
|
|
disk drivers are now smart enough to handle this correctly, as they
need to also handle pread(2)/pwrite(2).
ok deraadt@, krw@; ok marco@ on an similar, earlier diff
|
|
|
|
link->bus->sc_dev.dv_unit.
|
|
isn't it awesome that 5 out of 6 cases of this crap were in the various ppp
implementations? ok claudio ryan
the 6th to be fixed when we return from MEC
|
|
make sppp_flush use IFQ_PURGE instead of handrolling the same making
assumptions about ifqueue internals. ok ryan claudio
|
|
leaves an empty page in curpage, and this inconsistency slowly spreads
until finally one of the other pool checks freaks out.
ok art deraadt
|
|
ones that make assumptions about ifqueue internals... ok ryan claudio
|
|
why bother with APIs when you can muck with internals directly, it's obvious
there'll NEVER be changes, right. ok claudio ryan
|
|
|
|
the extraction loop should stop.
No more 298 pages in 42 segments when asking for only 32 pages in 1 segment.
ok oga@
|
|
Instead of allocating a crypto op and the optional dma buffer on each
and every io, preallocate a list of softraid crypto wus that contain a
buffer of the max size we will use (MAXPHYS). since we know the number
of openings we have in advance this means that on each io we just pick
one, shorten the list of crypto descs, init any values then do the io.
ok jsing (who provided many useful comments. he also provided a smarter way of
handling the cryptop lists which is not in this diff but will be implemented
soonish), marco@.
dlg@ pointed out that this should probably use iopools but letting
disciplines allocate their own iopool involves more softraid rejigging
that will have to be done first. For now this is sufficient.
|
|
|
|
devices must have an OpenBSD MBR partition to install /boot into.
But search anything except floppy devices (e.g. vnd) for such a
partition.
Feedback & ok deraadt@
|
|
a ffs frag size can be less than the d_secsize of the disk. Make
sure amd64 writedisklabel() puts the disklabel where readdoslabel()
will read it. Tweak i386/amd64 installboot/biosboot so sectors are
indeed used where sectors are claimed.
Lets me fdisk, newfs, mount and installboot onto 2048 and 4096
byte sector devices. Other filesystem utilites will still hold
surprises.
Note that actually booting from such devices will await BIOSen that
acknowledge such devices as bootable.
ok guenther@
|
|
i386 disobeys the Nth commandment. Fix this. While here, make i386 and amd64
definitions of iplclock and statclock match.
ok art@, kettenis@
|
|
the MSI enabled flag there such that the driver actually pays attention to it.
Found out the hard way by Chris Smith on an 82540EM, which defenitely does
not like MSI.
ok deraadt@
|
|
and a pool_init flag to aggressively run pool_chk. ok art deraadt
|
|
after_unlock code is needed if this happens, and running it was even
wrong because we weren't setting b_resid, so uio_offset (and higher
up, f_offset) would be incorrectly adjusted.
Discussed with deraadt@.
|
|
physio().
ok deraadt@
|
|
msync(size == 0) did strange things based on the original mapping
segments and trying to manipulate same. This code was copied from the
original vm when we moved to uvm.
posix says nothing about this behaviour and anything that depends on it is
systemically broken, so rip it out and make sys_msync about 30% smaller.
ok deraadt@, tedu@, guenther@.
|
|
|
|
|
|
|
|
ok guenther
|