| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
Try to tell what this really does.
Including a BUGS section on why it doesn't.
*roff code by wiz@, with some input from
Slava Semushin <slava.semushin@gmail.com>
ok millert
|
|
|
|
|
|
| |
Suggested by itojun@ in response to my getaddrinfo fixes.
OK millert@.
|
|
|
|
| |
OK itojun@.
|
|
|
|
| |
OK itojun@, moritz@, and millert@.
|
|
|
|
| |
ok jakob@
|
|
|
|
|
|
| |
calls with their reentrant versions.
OK millert@.
|
|
|
|
| |
found by Srebrenko Sehic, corrected by millert and claudio;
|
| |
|
|
|
|
| |
OK millert@.
|
|
|
|
| |
done by arc4random(); ok millert@ deraadt@
|
|
|
|
| |
to get random data without calling getpid(), ok millert@ deraadt@
|
| |
|
| |
|
|
|
|
| |
ok jmc@
|
| |
|
|
|
|
|
|
| |
called with user-supplied strings at the moment.
ok markus@
|
|
|
|
| |
4 hex digits between colons. deraadt ok
|
|
|
|
| |
in low-mem conditions; ok dim@
|
| |
|
| |
|
|
|
|
| |
send him feedback for these
|
|
|
|
|
|
|
|
|
|
| |
the kernel still handles RFC2292 set/getsockopts, so that compiled binary
has no trouble running. userland sees RFC3542 symbols only on header file
so new code has to use RFC3542 API.
bump libc shlib minor for function additions.
tested on i386/amd64 by jmc, i386 by brad. checked by deraadt.
|
| |
|
| |
|
|
|
|
|
|
| |
(to sync up with more recent IPv6 spec)
ok from: deraadt mcbride
|
| |
|
|
|
|
|
|
| |
<molivier at users dot sourceforge dot net>
ok jmc@ mickey@
|
|
|
|
| |
includes used a bit later (for instance on the vax)
|
|
|
|
|
| |
codebase. tested mostly by ckuethe and myself. __dtoa() use now requires
a call to __freedtoa()
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
create special allocators for pginfo and pgfree structs instead of imalloc.
this keeps them separated from application memory.
for chunks, to prevent deterministic reuse, keep a small array
and swizzle the to be freed chunk with a random previously freed chunk.
this last bit only for chunks because keeping arbitrarily large regions
of pages around may cause out of memory issues (and pages are, to some
extent, returned in random order).
all changes enabled by default.
thanks to ben for pointing out these issues.
ok tech@
|
|
|
|
| |
<bret dot lambert at gmail.com>; ok millert@ deraadt@
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
own brains out, and then takes lint down with it. To be investigated...
|
|
|
|
| |
ok miod@ drahn@
|
| |
|
|
|
|
|
|
| |
Log Message:
Switch from 4-clause to 2-clause BSD license.
Ok dillo@, board@.
|
|
|
|
| |
http://www.openssl.org/news/secadv_20060928.txt for more
|
|
|
|
|
|
| |
detctecion of underflow where it would otherwise not happen for FPUs
that have a larger register size than sizeof double (i386, m68k). ok
deraadt@ weingart@ kettenis@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adjust design of file descriptor table to eliminate races
with both opening and closing of file descriptor entries
and eliminates one class of deadlocks. One nice side effect
of this change in design should be better performance for
applications that open and close many file descriptors due
to reduced fd_table_lock contention and fd entry reuse.
- Add entry states to manage use of entry and eliminate
some closing races. fd entries are not deallocated upon
close() now.
- Call _thread_fd_table_init with one of five discreet
modes to properly initialize an entry and manage the
state transition to open.
- When closing an entry hold the entry spinlock locked
across the state transition and the _thread_sys_close
call to close another race.
- Introduce a new lock type FD_RDWR_CLOSE that transitions
either a closed entry or an open entry into closing state
and then waits for a RDWR lock so that the lock queue can
unwind normally. All subsequent fd lock attempts for that
entry are rejected with EBADF until the fd is fully closed,
or reopened by dup2(). Once a thread holds the FD_RDWR_LOCK
it is safe to close() it or dup2() on it.
- When a thread creates a new fd there is a window of time
when another thread could attempt to use the fd before the
creating thread has initialized the entry for it. This can
result in improper status_flags for the entry, so record
the entries init mode, detect when this has happened and
correct the status_flags when needed.
reviewed by marc@ & brad@, tested by several, okay brad@
|
|
|
|
|
|
| |
cool and recognizes __dead, and because shorter examples are clearer.
OK otto@.
|
|
|
|
|
| |
have multiple bits set, which lead to surprising results. Spotted by
Paul Stoeber. ok djm@
|
|
|
|
| |
OK djm@.
|
|
|
|
| |
OK otto@ and jaredy@.
|
|
|
|
|
|
|
|
|
| |
flag from its optional argument if permutation is disabled. The
idea was that since "r:" would match "-r foo" then "r::" should
match "-r foo" too as long as we know that things have not been
reshuffled. Unfortunately, this causes incompatibilities with GNU
getopt_long when the POSIXLY_CORRECT environment variable is set.
OK deraadt@
|
|
|
|
| |
ok beck@ miod@
|
|
|
|
|
|
| |
about them;
ok djm
|