| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
that might never be possible if the file was not opened in the corrent
mode. This prevents a hang for bad programs. Why do people code like that?
|
|
|
|
| |
seems to be tripping up a lot of applications.
|
|
|
|
|
| |
in the file descriptor table are exactly what the kernel knows subject
to the O_NONBLOCK flag being requested by the user.
|
|
|
|
|
|
| |
friend shmget().
PR: closes misc/6763
|
| |
|
|
|
|
|
|
| |
PR: 6903
Reviewed by: phk
Submitted by: Josh Gilliam <josh@quick.net>
|
|
|
|
|
|
|
| |
copy to bring these files into libc from libcompat. I will enable
them and kill off the libcompat versions on the main branch soon.
PR: step one toward closing misc/6763
|
| |
|
|
|
|
| |
Pointed out by: Charlie Sorsby <crs@hgo.net>
|
|
|
|
|
| |
lock debug into libc_r. I don't know if this is the best place to document
this, but at least it is recorded somewhere. 8-)
|
|
|
|
|
|
|
| |
line number every time a file descriptor is locked.
This looks like a big change but it isn't. It should reduce the size
of libc_r and make it run slightly faster.
|
|
|
|
|
|
|
| |
time that a thread keeps the file descriptor table locked. In particular,
perform malloc/free calls outside the lock and handle the situation
where two threads can race to initialise the table entry for the same
file descriptor.
|
|
|
|
|
|
|
|
|
|
| |
with -D_LOCK_DEBUG. This adds the file name and line number to each lock
call and these are stored in the spinlock structure. When using debug
mode, the lock function will check if the thread is trying to lock
something it has already locked. This is not supposed to happen because
the lock will be freed too early.
Without lock debug, libc_r should be smaller and slightly faster.
|
|
|
|
|
|
|
|
| |
cleanup destructor, so trap this case to prevent me from being being
burnt again by applications that try to do this. With this change, an
application (like one using a mis-configured ACE) will exit the process
after displaying a message quoting the POSIX section that the application
has violated.
|
|
|
|
|
| |
Add a thread specific flag to trap the case where pthread_exit() is
called from a destructor in violation of the Posix standard.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to destroy the RPC CLIENT handle before returning.
|
| |
|
| |
|
|
|
|
| |
to avoid recursive locking.
|
| |
|
| |
|
|
|
|
|
|
| |
Simplify the atomic lock prototype, removing the lock value.
Delete the unlock prototypes that are not required.
|
|
|
|
|
| |
Simplify the atomic lock to just write a value of 1 to the lock instead
of taking the value passed by the caller (which just confused things).
|
| |
|
|
|
|
| |
Pointed out by: "Steve Sims" <SimsS@IBM.Net>
|
|
|
|
|
|
| |
Also be consistent about usage of #if ...
Pointed out by: bde
|
|
|
|
|
| |
not supposed to happen, but I have seen bogus g++ code that causes
it.
|
|
|
|
|
|
| |
is allocated or not, rather than keeping a count and attempting to
know it it is in-use. POSIX says that once a key is deleted, using the
key again results in undefined behaviour.
|
| |
|
| |
|
|
|
|
|
| |
PR: 6868
Submitted by: Josh Gilliam <josh@quick.net>
|
|
|
|
| |
Pointed out by: Sue Blake <sue@welearn.com.au>
|
|
|
|
|
| |
state to running despite the SA_RESTART flag which is really just for
syscalls.
|
|
|
|
|
|
| |
Misc. cleanup
PR: 6825
Submitted by: Sergey Gershtein <sg@mplik.ru>
|
| |
|
| |
|
|
|
|
|
| |
PR: 6856
Submitted by: Josh Gilliam <josh@quick.net>
|
|
|
|
| |
NetBSD syscalls are defined in sys.mk if they are being used.
|
|
|
|
| |
don't try to use it to set special priorities.
|
|
|
|
|
| |
PR: 4043
Submitted by: Joe Orthoefer <j_orthoefer@tia.net>
|
|
|
|
|
|
|
|
|
| |
available and the kernel MIB setting is zero.
Return the result from getpagesize() if the p1003_1b.pagesize MIB
value is zero.
Suggested by: Joerg Schilling <schilling@fokus.gmd.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here is a some example for avoiding a confusion.
It asssumes a logged host domain is "spec.co.jp". All
example is longer than UT_HOSTNAMELEN value.
1) turbo.tama.spec.co.jp: 192.19.0.2 -> trubo.tama
2) turbo.tama.foo.co.jp : 192.19.0.2 -> 192.19.0.2
3) specgw.spec.co.jp : 202.32.13.1 -> specgw
Submitted by: Atsushi Murai <amurai@spec.co.jp>
|
|
|
|
|
|
| |
I shouldn't do things early in the morning.
[...]
I shouldn't do things early in the morning.
|
| |
|
|
|
|
| |
to wrapper them) and add a couple that should have been there.
|