| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
macros.
Add rb_foreach_next() and rb_foreach_reverse_prev(), which make it
possible to re-synchronize tree iteration after the tree has been
modified.
Rename rb_tree_new() to rb_new().
|
|
|
|
|
|
| |
o Stick with TLS Variant II for MIPS for the moment.
Approved by: imp
|
|
|
|
| |
Approved by: imp
|
|
|
|
| |
signed increment argument, but the size is an unsigned integer.
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
copied from ARM and modified to warrant the duplication. Oh,
and to make it work for PowerPC :-)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
occurred between 2001-2003. Thanks to bde for the history lesson[1]
concerning sys/types.h and the many system calls that at one time
(pre-2001) were required by POSIX to include it.
1. http://lists.freebsd.org/pipermail/freebsd-arch/2008-April/008126.html
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
| |
color bit in the least significant bit of the right child pointer, in
order to reduce red-black tree linkage overhead by ~2X as compared to
sys/tree.h.
Use the new red-black tree implementation in malloc, which drops
memory usage by ~0.5 or ~1%, for 32- and 64-bit systems, respectively.
|
|
|
|
|
|
|
|
| |
case of a file descriptor we can't handle, clear the FILE structure's flags
so it can be reused.
MFC after: 1 week
Reported by: otto @ OpenBSD
|
|
|
|
| |
Approved by: rwatson (mentor)
|
|
|
|
|
|
|
|
| |
conversion specifiers for them are present.
Submitted by: Maxim Dounin <mdounin@mdounin.ru>
Obtained from: NetBSD (partially)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
There were no checks for left and right precisions at all, and
a check for field width had integer overflow bug.
Reported by: Maksymilian Arciemowicz
Security: http://securityreason.com/achievement_securityalert/53
Submitted by: Maxim Dounin <mdounin@mdounin.ru>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
__sFILE. This was supposed to be done in 6.0. Some notes:
- Where possible I restored the various lines to their pre-__sFILEX state.
- Retire INITEXTRA() and just initialize the wchar bits (orientation and
mbstate) explicitly instead. The various places that used INITEXTRA
didn't need the locking fields or _up initialized. (Some places needed
_up to exist and not be off the end of a NULL or garbage pointer, but
they didn't require it to be initialized to a specific value.)
- For now, stdio.h "knows" that pthread_t is a 'struct pthread *' to
avoid namespace pollution of including all the pthread types in stdio.h.
Once we remove all the inlines and make __sFILE private it can go back
to using pthread_t, etc.
- This does not remove any of the inlines currently and does not change
any of the public ABI of 'FILE'.
MFC after: 1 month
Reviewed by: peter
|
|
|
|
|
|
| |
deals with the usual __opendir2() calls, and the rest part with an interface
translator to expose fdopendir(3) functionality. Manual page was obtained from
kib@'s work for *at(2) system calls.
|
|
|
|
|
| |
- Use /*- for copyright block;
- ANSIfy.
|
| |
|
|
|
|
| |
Submitted by: kib
|
|
|
|
| |
Reviewed by: ru
|
|
|
|
| |
when I have more brain cells to try again.
|
|
|
|
| |
included it.
|
| |
|
|
|
|
| |
PR: stand/107561
|
| |
|
|
|
|
| |
Pointy hat to yours truly.
|
|
|
|
| |
numbers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
|
|
|
|
|
|
| |
the wrong answer for virtually all inputs.
Thanks to remko for access to a sparc64 box for testing.
|
|
|
|
|
|
|
| |
flags appropriately. The next step is to make it raise a SIGFPE if
any exceptions are unmasked.
Thanks to remko for access to a sparc64 box for testing.
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
| |
to 8.0 belong in the FBSD_1.1 symbol namespace.
|
|
|
|
|
|
|
| |
struct flock with l_sysid member can work properly on an an old kernel which
doesn't support l_sysid.
Sponsored by: Isilon Systems
|
| |
|
|
|
|
| |
harsh reality.
|
| |
|
| |
|
|
|
|
|
| |
replace mutex with rwlock, this should eliminate lock contention in
most cases.
|
|
|
|
|
|
|
| |
Based on the submission by rdivacky,
sponsored by Google Summer of Code 2007
Reviewed by: rwatson, rdivacky
Tested by: pho
|
|
|
|
|
|
|
|
|
|
|
| |
__xdrrec_getrec has returned TRUE, then we have a complete request in
the buffer - calling xdrrec_skiprecord is not necessary. In particular,
if there is another record already buffered on the stream,
xdrrec_skiprecord will discard both this request and the next
one, causing the call to xdr_callmsg to fail and the stream to be
closed.
Sponsored by: Isilon Systems
|
|
|
|
| |
fragment header.
|
|
|
|
|
|
| |
live in libm, while modf() lives in libc due to historical
mistakes. I'm claiming in the manpage that they all live in libm,
since programmers should not rely on the mistake.
|
|
|
|
|
|
| |
hook it up to the build.
Reviewed by: brueffer (skeleton and formatting assistance)
|
|
|
|
|
|
| |
it up to the build.
Reviewed by: brueffer (skeleton and formatting assistance)
|
|
|
|
|
|
| |
"super" page or not.
Reviewed by: alc, ups
|
|
|
|
| |
Inspired by: phk
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
user-mode lock manager, build a kernel with the NFSLOCKD option and
add '-k' to 'rpc_lockd_flags' in rc.conf.
Highlights include:
* Thread-safe kernel RPC client - many threads can use the same RPC
client handle safely with replies being de-multiplexed at the socket
upcall (typically driven directly by the NIC interrupt) and handed
off to whichever thread matches the reply. For UDP sockets, many RPC
clients can share the same socket. This allows the use of a single
privileged UDP port number to talk to an arbitrary number of remote
hosts.
* Single-threaded kernel RPC server. Adding support for multi-threaded
server would be relatively straightforward and would follow
approximately the Solaris KPI. A single thread should be sufficient
for the NLM since it should rarely block in normal operation.
* Kernel mode NLM server supporting cancel requests and granted
callbacks. I've tested the NLM server reasonably extensively - it
passes both my own tests and the NFS Connectathon locking tests
running on Solaris, Mac OS X and Ubuntu Linux.
* Userland NLM client supported. While the NLM server doesn't have
support for the local NFS client's locking needs, it does have to
field async replies and granted callbacks from remote NLMs that the
local client has contacted. We relay these replies to the userland
rpc.lockd over a local domain RPC socket.
* Robust deadlock detection for the local lock manager. In particular
it will detect deadlocks caused by a lock request that covers more
than one blocking request. As required by the NLM protocol, all
deadlock detection happens synchronously - a user is guaranteed that
if a lock request isn't rejected immediately, the lock will
eventually be granted. The old system allowed for a 'deferred
deadlock' condition where a blocked lock request could wake up and
find that some other deadlock-causing lock owner had beaten them to
the lock.
* Since both local and remote locks are managed by the same kernel
locking code, local and remote processes can safely use file locks
for mutual exclusion. Local processes have no fairness advantage
compared to remote processes when contending to lock a region that
has just been unlocked - the local lock manager enforces a strict
first-come first-served model for both local and remote lockers.
Sponsored by: Isilon Systems
PR: 95247 107555 115524 116679
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
PR: 121490
Submitted by: Anatoly Borodin <anatoly.borodin@gmail.com>
Approved by: rwatson (mentor), jkoshy
MFC after: 3 days
|
|
|
|
| |
(Somehow this file sneaked from initial commit.)
|
| |
|