| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
build libkse. This should fix WITHOUT_LIBTHR builds as a side effect.
|
| |
|
|
|
|
| |
constructs in it.
|
|
|
|
|
|
| |
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.)
|
| |
|
|
|
|
| |
Reviewed by: davidxu
|
|
|
|
|
|
| |
- Restore the ability to debug kse coredumps in 8.0.
Suggested by: marcel
|
|
|
|
| |
time clock id.
|
| |
|
|
|
|
| |
Approved by: jkoshy(mentor), kientzle
|
|
|
|
|
| |
otherwise rwlock is recursivly called when signal happens and the __error
was never resolved before.
|
|
|
|
| |
unbreak it. We should really start compiling this with warnings.
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
any case safe.
|
|
|
|
|
|
| |
conformant to POSIX specification.
Bug reported by: modelnine at modelnine dt org
|
|
|
|
| |
for it, since the new thread will reduce it by itself.
|
|
|
|
| |
- Use a different sigmask variable name to avoid confusing.
|
|
|
|
| |
to speed up searching.
|
|
|
|
|
|
|
| |
consistent with the section indices returned to the application by
elf_ndxscn().
Submitted by: kaiw
|
|
|
|
|
|
|
|
|
| |
section header entry if the application is not taking charge of ELF
object layout.
Update (c) years, and bump the manual page's date.
Submitted by: kaiw
|
|
|
|
|
| |
Pointed-out by: Iain Hibbert < plunky at rya-online dot net >
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
(NAP, GN and PANU). No reason to not to support them.
Separate SDP parameters data structures for the BNEP based profiles.
Generalize Service Availability SDP parameter creation.
Requested by: Iain Hibbert < plunky at rya-online dot net >
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
_thr_suspend_check() which messes sigmask saved in thread structure.
- Don't suspend a thread has force_exit set.
- In pthread_exit(), if there is a suspension flag set, wake up waiting-
thread after setting PS_DEAD, this causes waiting-thread to break loop
in suspend_common().
|
|
|
|
|
|
|
| |
PR: 74743
Submitted by: knut st. osmundsen
Approved by: rwatson (mentor)
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of the array length needed to store all the directory entries.
Although BSD has historically guaranteed that st_size is the size
of the directory file, POSIX does not, and more to the point, some
recent filesystems such as ZFS use st_size to mean something else.
The fix is to not stat the directory at all, set the initial
array size to 32 entries, and realloc it in powers of 2 if that
proves insufficient.
PR: 113668
|
|
|
|
| |
be masked when it is resumed.
|
|
|
|
| |
longer runs once per entry.
|
| |
|
| |
|
|
|
|
|
|
|
| |
from the private archive_write structure and fix up all writers to use
the format fields in the base "archive" structure. This error made it
impossible to query the format after setting up a writer because the
write format was stored in an inaccessible place.
|
|
|
|
| |
Pointy hat: me
|
|
|
|
|
|
| |
"file" is described by multiple "lines" each possibly containing
multiple "keywords." Incorporate some additions from Joerg Sonnenberger
to handle linked files and correctly deal with backing files on disk.
|
|
|
|
| |
Correct the nasty typo this uncovers.
|
|
|
|
|
|
| |
Disable the use of PaxHeader.<pid> for the fake pax extension pathname
until I can make the name here settable. Otherwise, tests that try
to compare output to static pre-generated reference files break.
|
| |
|
|
|
|
| |
fake directory name used for pax extended headers.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(including pathname, gname, uname) be stored in UTF-8. This usually
doesn't cause problems on FreeBSD because the "C" locale on FreeBSD
can convert any byte to Unicode/wchar_t and from there to UTF-8. In
other locales (including the "C" locale on Linux which is really
ASCII), you can get into trouble with pathnames that cannot be
converted to UTF-8.
Libarchive's pax writer truncated pathnames and other strings at the
first nonconvertible character. (ouch!) Other archivers have worked
around this by storing unconvertible pathnames as raw binary, a
practice which has been sanctioned by the Austin group. However,
libarchive's pax reader would segfault reading headers that weren't
proper UTF-8. (ouch!) Since bsdtar defaults to pax format, this
affects bsdtar rather heavily.
To correctly support the new "hdrcharset" header that is going into
SUS and to handle conversion failures in general, libarchive's pax reader
and writer have been overhauled fairly extensively. They used to do
most of the pax header processing using wchar_t (Unicode); they now do
most of it using char so that common logic applies to either UTF-8 or
"binary" strings.
As a bonus, a number of extraneous conversions to/from wchar_t have
been eliminated, which should speed things up just a tad.
Thanks to: Bjoern Jacke for originally reporting this to me
Thanks to: Joerg Sonnenberger for noting a bad typo in my first draft of this
Thanks to: Gunnar Ritter for getting the standard fixed
MFC after: 5 days
|
| |
|
|
|
|
|
| |
return a NULL instead of an incomplete string. Expand the test coverage
to verify the correct behavior here.
|
|
|
|
|
|
|
| |
rely on a deprecated value to set the default. This is also
related to a longer-term goal of setting the default block
size based on format and possibly other factors, which makes
it a bad idea to tie this to a published constant.
|
|
|
|
|
| |
override the currently set link value, whether that's a hardlink
or a symlink. Plus documentation update and tests.
|
|
|
|
| |
namespace problems.
|