| Age | Commit message (Collapse) | Author |
|---|
|
This commit ports the infrastructure to do binary code patching from amd64.
The existing code patching for SMAP is converted to the new infrastruture.
ok kettenis@
"should go in" deraadt@
|
|
reading a timestamp off the render ring for the Mesa i965 driver.
ok kettenis@
|
|
|
|
Found by inspection while curious... not though actual experience...
ok miod
|
|
interpretation of it isn't quite right. So instead of allocating memory
and slicing it based on the parameters returned by CPUID, simply use a member
in struct cpu_info like basically all other OSes out there do. Our struct
cpu_info is large enough to never cause any overlap. This makes the
mwait-based idle loop actually work. We still execute the CPUID instruction
to make sure monitor/mwait is properly supported by the hardware we're
running on.
ok sthen@, deraadt@, guenther@
|
|
handling along the way.
Reviews by Brendan MacDonell, Jeremy Devenport, florian, doug, millert
|
|
man_node() from the mandoc(3) semi-public interface and the internal
wrapper functions print_mdoc() and print_man() from the HTML formatters.
Minus 60 lines of code, no functional change.
|
|
Minus 80 lines of code, no functional change.
Written on the train from Koeln to Wolfsburg returning from p2k15.
|
|
and call them from mparse_alloc() and choose_parser(),
preparing unified allocation of struct roff_man.
|
|
arguments of mparse_result() by one. No functional change.
Written on the ICE Bruxelles-Koeln on the way back from p2k15.
|
|
Almost completely mechanical, no functional change.
Written on the train from Exeter to London returning from p2k15.
|
|
|
|
From brad@
|
|
don;t try to list all generations in ciss's Nd;
do not use all caps for "array"
|
|
discussed with kettenis
|
|
these in future we should add i915_debugfs.c
|
|
mbuf_list.
hfsc lists are very clever because they manage a fifo with a single
pointer by abusing the m_next pointer of the tail mbuf to point to
the head. clever but hard to read.
mbuf_lists are slightly bigger because they explicitely track the
head mbuf, but i got us that space back by inlining hfsc_classq
into hfsc_class and removing the unnecessary classq field.
ok henning@
|
|
|
|
error path.
|
|
newlines which could lead to http response splitting/smuggling
if a badly behaved proxy is in front of httpd.
Switch from evbuffer_readline() to evbuffer_readln() with
EVBUFFER_EOL_CRLF_STRICT to avoid this.
ok florian@
|
|
EIP/RIP adjustment for ERESTART
ok mlarkin@
|
|
Don't cast file sizes to size_t when comparing file contents for the -C option
ok deraadt@
|
|
allowing the addition of more accurate bounds and garbage checks.
ok millert
|
|
to parse tz_minuteswest.
ok millert
|
|
get padding appended to them. This padding is not stripped off in
ip6_input() (due to support for IPv6 Jumbograms, RFC2675). That
means PF needs to be careful when reassembling fragmented packets
to not include the padding in the reassembled packet.
from FreeBSD; via Kristof Provost; OK henning@
|
|
this wording change was made a while ago but got accidentally reverted
|
|
found by Jukka Taimisto and Markus Hietava
|
|
fix a few errors that were being printed to stdout instead of stderr
and a few non-errors that were going to stderr instead of stdout
bz#2325; ok dtucker
|
|
requested; bz#1682 ok dtucker@
|
|
MUTEX_ASSERT_UNLOCKED, but it turns out alpha mutexes arent very
friendly to diagnostics on smp systems.
alpha mutexes contained an mtx_lock member. when 0 the mutex was
unlocked, and when 1 it was locked. the MUTEX_ASSERT_UNLOCKED checked
if mtx_lock was 1 to see if the current cpu owned the mutex, but
in an mp system another cpu may have set mtx_lock to 1, which causes
the assert to fire.
this changes alpha mutexes so they record which cpu owns the lock
rather than just if the lock is held or not. the diagnostics compare
the owner to the current cpus curcpu() address so they can actually
tell if the current cpu holds the lock instead of whether any cpu
holds the lock.
instead of using custom asm to implement a cas this uses atomic_cas_ptr,
which on alpha uses gcc cas code. miod says he has far more confidence
in the gcc cas than the code that was there before.
while im here i also shuffled the code. on MULTIPROCESSOR systems
instead of duplicating code between mtx_enter and mtx_enter_try,
mtx_enter simply loops on mtx_enter_try until it succeeds.
this also provides an alternative implementation of mutexes on
!MULTIPROCESSOR systems that avoids interlocking opcodes. mutexes
wont contend on UP boxes, theyre basically wrappers around spls.
we can just do the splraise, stash the owner as a guard value for
DIAGNOSTIC and return. similarly, mtx_enter_try on UP will never
fail, so we can just call mtx_enter and return 1.
ok miod@
|
|
|
|
No objection from reyk@, OK markus, hshoexer
|
|
returned by IPsec-enabled NICs; OK markus, hshoexer
|
|
|
|
in its way.
|
|
|
|
wasn't updated, so we would crash when doing `bgpctl net bulk` commands.
Fix by moving parse_prefix into a header, since we use it in more than
one file.
crash found by henning@
underlying problem found by blambert@
OK sthen@ deraadt@ claudio@ henning@
|
|
and remove redundant loopback cloning route.
Note that tests using IPv6 still contain two routes to "::1" this should
cause no harm but is being investigated.
|
|
all the entropy provided by the device.
Also make sure we match the right endpoint.
From Sean Levy based on comments from Andreas Gustafsson who's behind
Alea.
|
|
but never actually did so. Fix that so that we stop losing the
second argument to {get,set}sockopt(). Handling of levels other than
SOL_SOCKET could be improved.
|
|
family. (sysctl(3) is practically the only place where PF_* is correct)
|
|
atime and mtime are UTIME_OMIT (at least for ufs, tmpfs, and ext2fs), and
to correctly handle a timestamp of -1.
ok millert@
|
|
bz#278 reported by drk AT sgi.com; ok dtucker
|
|
HostCertificate. bz#2346, patch from jjelen at redhat com, ok djm.
|
|
ok kettenis@
|
|
bz#2382, feedback from jmc@, ok djm@
|
|
in rev. 1.225. Regression reported by florian@.
|
|
|
|
|
|
|
