Age | Commit message (Collapse) | Author |
|
initialized. Calling malloc(9) at that point is not a good idea. So
initialize consbuf later.
Fixes dmesg -s on sparc64 (and probably a few other architectures).
ok miod@, deraadt@
|
|
Help and feedback by Theo and Miod.
OK deraadt@, manpage-ok jmc@
|
|
reported and revert tested by krw
|
|
must do that. otherwise, pmap_kremove is called twice. i386 in particular
does not tolerate that, found by sebastia
ok mlarkin kettenis
|
|
change on us. also, remove unused second arg to bufq_wait.
from pedro at bitrig via david hill.
ok beck kettenis
|
|
|
|
(accuracy of variable names, aside)
ok kettenis
|
|
an interrupt handler at an ipl level higher than what you're
splasserting you should be at. if you think code should be protected
by IPL_BIO and its entered from an interrupt handler established
at IPL_NET, you have a bug.
add some asserts to gets and puts so we can pick those cases up.
|
|
landisk machines. we've been unable to figure out due to a lack of
hardware (on my part) or time.
discussed with and ok miod@
|
|
pool_setlowat()
ok dlg@ tedu@
|
|
|
|
Diff from dlg@.
ok jsing@
|
|
architectures.
|
|
before you, to see their files reduced to ashes, to see those who
love them shrouded in tears, and to gather into your API all their
invocations.
In other words, workq is no more. There is only taskq.
ok kettenis@ dlg@ (creator of taskq) jmc@
|
|
disks) with taskq. Diff originally from blambert@.
ok kettenis@
|
|
|
|
(which we never did, but it was a bug nonetheless).
ok kettenis, deraadt
|
|
(and therefore no interpreter). Necessary to make self-relocating "static"
PIE working.
This will also allow execution of shared libraries that have the 'x' bit set.
Those shouldn't exist, but unfortunately people outside OpenBSD think
differently which means third-party software sometimes installs shared
libraries with the 'x' bit set.
ok kurt@, deraadt@
|
|
|
|
8 items on a page. this reduces the number of allocator operations
we have to do per item on large items.
ok tedu@
|
|
|
|
by passing random stack garbage as the size to free(9).
From David Imhoff
|
|
|
|
marker for which pools are not interrupt safe. ok dlg
|
|
a second.
this basically brings back the functionality that was trimmed in r1.53,
except this version uses ticks instead of very slow hardware clock reads.
ok tedu@
|
|
latter is cheaper, but i forgot to change the thing that pulls pages off
those lists to match the change in direction. the page lists went from LIFO
to FIFO.
this changes pool_update_curpage to use TAILQ_LAST so we go back to LIFO.
pointed out by and ok tedu@
|
|
either end of the lists cheaply.
ok kettenis@ tedu@
|
|
era. fix uvm including c files to include lock.h or atomic.h as necessary.
ok deraadt
|
|
doesn't have all the values and therefore can't be used everywhere.
ok deraadt@ kettenis@
|
|
objective: vnode.h doesn't include uvm_extern.h anymore.
followup changes: include uvm_extern.h or lock.h where necessary.
ok and help from deraadt
|
|
eliminating the must-be-kept-in-sync UVM_INH_* macros
ok deraadt@ tedu@
|
|
ok tedu@ deraadt@
|
|
controls whether you can ptrace any process with appropriate privileges
or only one own's children.
ok deraadt
|
|
Previous version OK'ed by tedu@ deraadt@
|
|
|
|
|
|
|
|
ok deraadt, tests on glxpcib and ok mpi
|
|
|
|
ok deraadt@ tedu@
|
|
|
|
|
|
|
|
OK deraadt@
|
|
This adds a new sysctl KERN_PROC_VMMAP, which returns an array of VM map
entries of a specified process. This prevents debuggers from iterating
vm_map_entry RB tree via kvm(3).
The name KERN_PROC_VMMAP and struct kinfo_vmentry are chosen from the same
function in FreeBSD. struct kinfo_vmentry is revised to reduce size, because
OpenBSD does not keep track of filepaths. The semantic is also changed to
return max buffer size as a hint, and start iteration at the specified base
address.
Much valuable input from deraadt@, guenther@, tedu@
OK tedu@ deraadt@
|
|
pool hasnt had pool_setipl called.
ok kettenis@ ages ago
|
|
|
|
flag if the falloc() fails
reported by Carlin Bingham (cb (at) viennan.net)
ok deraadt@ tedu@
|
|
dynamic clamping mechanism. In the (new? has it already been 20 years?)
world of tty ring buffers, c_cn is the maximum...
There could be some ugly limit elsewhere, which may cause a deadlock
(dug as deep as my patience allows), so please report any sort
of new console or xterm issues that show up, such as tty lockups or high
cpu utilization..
|
|
|