| Age | Commit message (Collapse) | Author |
|---|
|
mentioned.
accidently already slipped in w/ my last commit; this one is forced.
ok theo
|
|
aborting with a syntax error
|
|
|
|
- sparc -> hppa in hppa/MAKEDEV.8
- removed references to wscons from mac68k/MAKEDEV.8
- typos
ok deraadt@
|
|
Work started with revision 1.4
ok dhartmei@
|
|
|
|
If the fpu isn't enabled, don't save state, otherwise, save the state,
mark both sides clean and disable the fpu.
On restore:
If the saved fpu state has the fpu disabled, do nothing, otherwise, restore
everything.
|
|
edit, just stash it once in copyfile(). This fixes the check for
whether or not changes have been made (based on the timestamp) for
cases like when the _shadow group is missing but is fixed by the
admin during the next edit.
|
|
|
|
an arch/i386 patch previously commited and arch/sparc64 patches
from jason@ make the preemption_float test pass on those two
architectures.
Do not run signal handlers for a thread until the thread has
been made current, ensuring the proper context. Solves several
(if not all) of the '_pq_insert_tail: Already in priority queue'
problems.
|
|
|
|
eg. normalization -> normalisation
- examples/commands in white bold face
- .Pa macros -> .Ar
- ordered SEE ALSO
- removed double quotes from GRAMMAR section
- some grammar typos
ok deraadt@
|
|
|
|
|
|
|
|
Fix it.
millert@ ok
|
|
copies the data to the specified buffer. So, for TCP options, provide
an sufficiently large buffer and copy to there.
|
|
doing it later can invalidate pointers to mbuf data. This fixes subtle
breakage just introduced (with 1.306).
|
|
|
|
before as you cannot specify "bandwidth 0b" on a rule; now that rate2str is
used for the stats output it does matter.
|
|
Interestingly, our own stack uses wscale 1 quite regularly, and I now
suspect that this is what caused most of the state failures I've seen.
They were quite rare, but with working wscale support, they are reduced
even more. ok henning@
|
|
|
|
cbq only for now.
|
|
|
|
|
|
|
|
This allows us to remove some ambiguities on how some functions are called,
remove some diagnostic checks for conditions that can never happen and
remove the ugly hack with "pmap_initialized".
Then, rework internal function interfaces and some logic so as to stop
fetching vm_page from a pa and the reverse every now and then - this makes
some pmap operations run much faster.
While there, various KNF and whitespace fixes, and rename some structure
fields to be closer to the m68k pmap.
per art@'s idea.
|
|
|
|
|
|
|
|
executable regions which are writable. If a section of an executable is
writable and executable, it is much easier for errant code to modify the
executable's behavior.
Two current areas in shared library environments which have this
critical problem are the GOT (Global Offset Table) and PLT (Procedure
Linkage Table). The PLT is required to be executable and both GOT and
PLT are writable on most architectures. On most ELF architecture
machines this would cause shared libraries to have data and BSS marked
as executable.
Padding to the linker script for programs and shared libraries/objects
to isolate the GOT and PLT into their own load sections in the
executables. This allows only the text(readonly) region and the PLT
region to be marked executable with the normal data and BSS not marked
as executable. The PLT region is still marked executable on most
architectures because the PLT lives in the "data" or "BSS" regions
and the dynamic loader will need to modify it. Since the GOT and PLT
should only ever be written by the dynamic linker, it will be modified
to mprotect those regions so that they are not writable during normal
execution. If the dynamic linker needs to modify the regions later,
(eg for lazy binding), it will mprotect the region, make the necessary
changes, and mprotect it back. Since it is possible to receive a
signal which would interrupt the program flow and perhaps cause the
dynamic linker to modify the same (or nearby) PLT references, it is now
necessary for signals to be blocked for the duration of the mprotect.
This diff was omitted from the original commit, this implements the
-Z option to produce traditional (non protected) executables.
|
|
|
|
present. Fixes illegal instruction problems seen the last few days
tested by myself and matthieu@
|
|
|
|
- reading RX_COMPLETION is a waste of time (and a -slow- PCI read vs. an,
albeit uncached, memory access to determine the same thing).
- on RX_OVERFLOW, reset the board; the RX unit has probably wedged
|
|
|
|
disable support for Update-prog and Checkin-prog. This is a good
idea for anonymouse cvs servers or anyone who doesn't need this
feature. From Stefan Esser.
|
|
wi_mgmt_xmit: xmit failed messages; millert@ testing and ok
|
|
|
|
|
|
|
|
|
|
private agent key is used; with djm@; test by dugsong@, djm@; ok deraadt@
|
|
- Macros and Tables can appear anywhere in pf.conf
- Since tables are no longer just a rule option, move the section up
appropriately.
ok dhartmei@
|
|
This only happens when using nat/rdr/binat on IPv6 connections, which
hasn't been used before, obviously. But it does work now.
Reported and confirmed by evilted@efnet, ok mcbride@
|
|
ok millert@
|
|
|
|
|
|
Help with english language jmc@
ok dhartmei@ cedric@
|
|
|
